HighGHSA-4r76-xr68-w7m7
TYPO3 may allow editors to change, create, or delete metadata of files not within their file mounts
Published 30 May 2024 · Updated 5 Dec 2024
Affected packages
typo3/cmsComposer
- Affected
- >=6.2.0 <6.2.14
- Fixed in
- 6.2.14
Update to the fixed version for your release line, for example:
composer require typo3/cms:^6.2.14typo3/cmsComposer
- Affected
- >=7.0.0 <7.3.1
- Fixed in
- 7.3.1
Update to the fixed version for your release line, for example:
composer require typo3/cms:^7.3.1Details
It has been discovered, that editors with access to file meta data table could change, create or delete metadata of files which are not within their file mounts.
Is GHSA-4r76-xr68-w7m7 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/typo3/commit/0decbf83c531cab77497429eb2edecf9a1038b25
- Linkgithub.com/TYPO3/typo3/commit/bff9fa5945801d1d2c641ddc8eb86c6647549d80
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2015-07-01-1.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2015-002
- Linktypo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2015-002
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.