Loading vulnerability…
CVE-2014-3577 is an incomplete fix for CVE-2012-6153 in the SSL hostname-verification logic of org.apache.http.conn.ssl.AbstractVerifier. Apache HttpComponents HttpClient before 4.3.5 and HttpAsyncClient before 4.0.2 can incorrectly extract and validate a hostname from an X.509 certificate distinguished name. A CN-formatted string embedded in a non-CN distinguished-name attribute can be interpreted as the server Common Name, allowing a certificate that does not legitimately identify the requested host to pass hostname verification.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
83 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Apache HttpComponents Client SSL/TLS hostname-verification bypass caused by flawed parsing of the X.509 certificate subject Common Name. A MITM attacker can craft a certificate subject such as O="foo,CN=www.apache.org" so that the client incorrectly extracts a trusted hostname from another subject attribute.
An Apache HttpComponents HttpClient SSL/TLS hostname-verification bypass caused by flawed parsing of the Common Name field in an X.509 certificate subject. A MITM attacker could use a specially crafted certificate subject to impersonate a server.
An SSL/TLS hostname-verification bypass in Apache HttpComponents Client caused by flawed parsing and validation of the X.509 subject Common Name. An on-path attacker could spoof a server with a specially crafted certificate and conduct a man-in-the-middle attack.
An Apache HttpComponents/Commons HttpClient SSL hostname-verification bypass caused by flawed parsing of the X.509 subject Common Name. A MITM attacker could spoof a server using a specially crafted certificate.
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.