Loading vulnerability…
CVE-2011-2894 is an unsafe Java deserialization vulnerability in Spring Framework 3.0.0 through 3.0.5 and Spring Security 3.0.0 through 3.0.5 and 2.0.0 through 2.0.6. The affected components deserialize attacker-controlled objects without sufficient type or trust restrictions. An attacker can exploit Java Proxy objects with a controlled InvocationHandler, or access internal Spring AOP interfaces, to bypass intended security restrictions. A demonstrated path deserializes a DefaultListableBeanFactory object and invokes functionality that reaches the Java runtime command-execution interface.
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 is a proof-of-concept (PoC) exploit for CVE-2011-2894, a remote code execution vulnerability in the Spring Framework (Java). The main exploit logic is implemented in 'src/main/java/org/pwntester/springbreaker/FactoryProxySerializationExploit.java', which programmatically constructs a malicious Spring bean factory and serializes a proxy object to 'proxy.ser'. When this serialized object is deserialized by a vulnerable Spring application (as demonstrated in 'src/main/java/com/company/SerializationServer.java'), it triggers the execution of an arbitrary system command (by default, launching Calculator on macOS, but this can be changed). The repository includes supporting model classes and shell scripts for building and running the exploit and server. The exploit demonstrates how an attacker can achieve arbitrary code execution via Java deserialization and Spring bean manipulation, targeting applications that deserialize untrusted data. No network endpoints are hardcoded, but the attack vector can be both local (file-based deserialization) and remote (if the vulnerable application accepts serialized objects 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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Spring deserialization remote code execution vulnerability referenced in the presentation as prior work related to unsafe deserialization and gadget-based exploitation.
Spring Framework deserialization vulnerability allowing arbitrary code execution from untrusted object sources.
A Spring Framework unsafe-deserialization vulnerability permitting arbitrary code execution through objects from untrusted sources.
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.