Skip to content
Fencer Intel
high —

GHSA-vh6j-wv25-8qxr json

Flow Bugfix Releases for Entity Security

published 2y ago modified last yr.

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

If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them.

Patch / fix

  • packagist typo3/flow 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6

Is GHSA-vh6j-wv25-8qxr 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 typo3/flow
>=3.0.0, <3.0.12
>=3.1.0, <3.1.10
>=3.2.0, <3.2.13
>=3.3.0, <3.3.13
>=4.0.0, <4.0.6
3.0.12
3.1.10
3.2.13
3.3.13
4.0.6

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.