CVE-2020-15098 json
Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS
published 6y ago modified 4mo ago also BIT-typo3-2020-15098 , EUVD-2020-0564 , GHSA-m5vr-3m74-jwxp
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.20, and greater than or equal to 10.0.0 and less than 10.4.6, it has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains including potential privilege escalation, insecure deserialization & remote code execution. The overall severity of this vulnerability is high based on mentioned attack chains and the requirement of having a valid backend user session (authenticated). This has been patched in versions 9.5.20 and 10.4.6.
Patch / fix
- packagist typo3/cms-core 9.5.20, 10.4.6
- packagist typo3/cms 9.5.20, 10.4.6
- bitnami typo3 9.5.20, 10.4.6
- typo3 typo3 9.5.20, 10.4.6
Is CVE-2020-15098 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 FencerExploit prediction
2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| OSV | 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-core | >=9.0.0, <9.5.20 >=10.0.0, <10.4.6 |
9.5.20 10.4.6 |
| packagist | typo3/cms | >=10.0.0, <10.4.6 >=9.0.0, <9.5.20 |
10.4.6 9.5.20 |
| bitnami | typo3 | >=9.0.0, <9.5.20 >=10.0.0, <10.4.6 |
9.5.20 10.4.6 |
Affected products
- TYPO3 TYPO3 CMS
Classification
References
-
github.com
/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99ef53f4b561114acfa9e5c47e1
web, broken-link
-
typo3.org
/security/advisory/typo3-core-sa-2016-013
web, vendor-advisory
-
typo3.org
/security/advisory/typo3-core-sa-2020-008
web, vendor-advisory
-
github.com
/TYPO3/TYPO3.CMS/security/advisories/GHSA-m5vr-3m74-jwxp
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2016-5091
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15098
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-15098.yaml
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-15098.yaml
web
-
github.com
/TYPO3/TYPO3.CMS
package
Sources
- CVE List CVE-2020-15098
- GitHub Advisory GHSA-m5vr-3m74-jwxp
- NVD CVE-2020-15098
- OSV BIT-typo3-2020-15098
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.