Loading vulnerability…
Apache Groovy 1.7.0 through 2.4.3 contains a deserialization vulnerability in the MethodClosure class implemented in runtime/MethodClosure.java. A crafted serialized object can be supplied to vulnerable code paths that deserialize untrusted data, allowing attacker-controlled object state to be reconstructed and abused during deserialization. The flaw can be triggered remotely where an application accepts attacker-influenced serialized objects, and successful exploitation can result in arbitrary code execution or denial of service.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Groovyにおけるデシリアライズ関連のコード実行脆弱性として比較例で言及。
A related Groovy vulnerability referenced for context, but not described in detail in the content.
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.