Loading vulnerability…
TYPO3 versions 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 generate the TYPO3 encryption key through the System extension Install tool using a seed derived from system time. The predictable seed substantially reduces the uncertainty of the generated cryptographic key and makes offline key-recovery attempts more feasible.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit auxiliary module targeting TYPO3 installations vulnerable to CVE-2009-0255 (TYPO3-SA-2009-001). The exploit abuses a weakness in the encryption key generation for the jumpUrl mechanism, allowing attackers to disclose arbitrary files from the server by brute-forcing or supplying a known encryption key. The module is written in Ruby and leverages Metasploit's HTTP client functionality to craft requests to the vulnerable TYPO3 endpoint (typically /index.php with specific parameters). The default target file is typo3conf/localconf.php, but any file accessible to the web server user can be specified. The exploit is operational and can be used to retrieve sensitive files from affected TYPO3 servers over the network.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability where a cryptographic key is generated using a system-time-based seed, making the key more predictable.
A cryptographic key was generated from a system-time-based seed, making its randomness predictable.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.