Skip to content
Fencer Intel
low —

GHSA-9m6v-8fxc-4r44 json

Sulu: Used API Keys may be available via Admin API

published 5mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

The users endpoint controller exposes a project's apiKey field to the logged-in user, provided they have permission for that endpoint. This only has impact if a project itself uses that specific field, Sulu itself does nothing with it and has no authentication per apiKey in its core.

### Patches

A patch is released with Version 2.6.23 and 3.0.5.

### Workarounds

Remove the field descriptor by patch the UserController.php File in Sulu Security Bundle.

Patch / fix

  • packagist sulu/sulu 2.6.23, 3.0.6

Is GHSA-9m6v-8fxc-4r44 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist sulu/sulu
>=3.0.0-alpha1, <3.0.6
<2.6.23
3.0.6
2.6.23

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.