HighGHSA-m5vr-3m74-jwxpBIT-typo3-2020-15098CVE-2020-15098

Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS

Published 29 Jul 2020 · Updated 8 Jul 2026

Affected packages

typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.20
Fixed in
9.5.20
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.20
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.6
Fixed in
10.4.6
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.6
typo3/cmsComposer
Affected
>=10.0.0 <10.4.6
Fixed in
10.4.6
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.6
typo3/cmsComposer
Affected
>=9.0.0 <9.5.20
Fixed in
9.5.20
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.20

Details

> ### Meta > * CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (8.2) > * CWE-325, CWE-20, CWE-200, CWE-502

Problem

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 as described below.

  • TYPO3-CORE-SA-2020-007, CVE-2020-15099: Potential Privilege Escalation + the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network) + CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (7.5, high)
  • TYPO3-CORE-SA-2016-013, CVE-2016-5091: Insecure Deserialization & Remote Code Execution + an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation + CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (9.1, critical)

The overall severity of this vulnerability is high (8.2) based on mentioned attack chains and the requirement of having a valid backend user session (authenticated).

Solution

Update to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.

Credits

Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.

References

Is GHSA-m5vr-3m74-jwxp 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-core, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.