Loading vulnerability…
TYPO3's jumpUrl (access-tracking) implementation improperly compares certain hash values when making access-control decisions. In TYPO3 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4, this flaw can allow a remote attacker to bypass the intended access control and read arbitrary files through unspecified vectors.
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 (1 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/admin/http/typo3_sa_2010_020.rb) that exploits CVE-2010-3714, a remote file disclosure vulnerability in TYPO3's jumpurl feature. The module allows an attacker to retrieve arbitrary files from the TYPO3 server by abusing a flaw in the hash matching mechanism (juHash=0). The attacker can specify the file to retrieve (default: typo3conf/localconf.php) and the path to the TYPO3 installation. The exploit works by sending a large number of crafted HTTP GET requests to the /index.php endpoint with specific parameters. If successful, the contents of the targeted file are saved as loot. The module is operational and requires the attacker to know or guess the file path. The only file in the repository is the Metasploit module itself, written in Ruby.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.