Cleartext storage of session identifier
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.2.57, 7.6.51, 8.7.40, 10.4.14, 11.1.1, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 user session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system. This is fixed in versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1.
Timeline
- CVE published
- Record last updated
Affected versions
- TYPO3 TYPO3.CMS
From 6.2.0 · through 6.2.56; From 7.0.0 · through 7.6.50; From 8.0.0 · through 8.7.39; From 9.0.0 · through 9.5.24; From 10.0.0 · through 10.4.13; From 11.0.0 · through 11.1.0
- typo3/cms-corePackagist
From 6.2.0 · fixed in 6.2.57
- typo3/cms-corePackagist
From 7.0.0 · fixed in 7.6.51
- typo3/cms-corePackagist
From 8.0.0 · fixed in 8.7.40
- typo3/cms-corePackagist
From 10.0.0 · fixed in 10.4.14
- typo3/cms-corePackagist
From 11.0.0 · fixed in 11.1.1
- typo3/cms-corePackagist
From 9.0.0 · fixed in 9.5.25
- typo3/cmsPackagist
From 10.0.0 · fixed in 10.4.14
- typo3/cmsPackagist
From 11.0.0 · fixed in 11.1.1
- typo3/cmsPackagist
From 9.0.0 · fixed in 9.5.25