CVE-2009-0255 json
The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key wit…
published 2009-01-22 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0263
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.4%
- EPSS 9.4% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Metasploit
Summary
The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key with an insufficiently random seed, which makes it easier for attackers to crack the key.
Patch / fix
- typo3 typo3 4.0.10, 4.1.8, 4.2.4
Timeline
- First public exploit (Metasploit auxiliary/admin/http/typo3_sa_2009_001)
- Published
Exploit prediction
9.44% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/admin/http/typo3_sa_2009_001 TYPO3 sa-2009-001 Weak Encryption Key File Disclosure metasploit auxiliary, normal rank, 2009-01-20
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-330 Use of Insufficiently Random Values
References
-
debian.org
/security/2009/dsa-1711
vendor-advisory, mailing-list
-
typo3.org
/teams/security/security-bulletins/typo3-sa-2009-001/
vendor-advisory
-
secunia.com
/advisories/33617
third-party-advisory, broken-link, vendor-advisory
-
secunia.com
/advisories/33679
third-party-advisory, broken-link, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/48132
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/33376
vdb-entry, broken-link, third-party-advisory
Sources
- CVE List CVE-2009-0255
- NVD CVE-2009-0255
Fencer Vulns 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.