GHSA-4r76-xr68-w7m7 json
TYPO3 may allow editors to change, create, or delete metadata of files not within their file mounts
published 2y ago modified last yr.
- cvss
- 8.8
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist typo3/cms 6.2.14, 7.3.1
- github.com/TYPO3/typo3@0decbf8 commit
- github.com/TYPO3/typo3@bff9fa5 commit
Is GHSA-4r76-xr68-w7m7 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms | >=6.2.0, <6.2.14 >=7.0.0, <7.3.1 |
6.2.14 7.3.1 |
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/TYPO3/typo3/commit/0decbf83c531cab77497429eb2edecf9a1038b25
web
-
github.com
/TYPO3/typo3/commit/bff9fa5945801d1d2c641ddc8eb86c6647549d80
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2015-07-01-1.yaml
web
-
github.com
/TYPO3/typo3
package
-
typo3.org
/security/advisory/typo3-core-sa-2015-002
web
-
typo3.org
/teams/security/security-bulletins/typo3-core/typo3-core-sa-2015-002
web
Sources
- GitHub Advisory GHSA-4r76-xr68-w7m7
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.