Loading vulnerability…
CVE-2024-20931 is an easily exploitable vulnerability in the Core component of Oracle WebLogic Server, affecting versions 12.2.1.4.0 and 14.1.1.0.0. The issue is reachable remotely over the T3 and IIOP protocols and can be exploited by an unauthenticated attacker with network access to the vulnerable service. Successful exploitation compromises the confidentiality of data accessible to the WebLogic Server instance, allowing unauthorized access to critical data or potentially complete access to all data available to the server. Specific vulnerable functions or code paths are not identified in the available information.
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 proof-of-concept exploit for CVE-2024-20931, targeting Oracle WebLogic Server. The main file, CVE_2024_20931.java, demonstrates a JNDI injection attack by creating a ForeignOpaqueReference object with its JNDI environment and remote JNDI name set to reference an attacker-controlled RMI server (rmi://127.0.0.1:1099/ygevmj). The exploit binds this object to the WebLogic JNDI context (t3://127.0.0.1:7001) under the name 'glassy' and attempts to trigger a lookup, which could result in remote code execution if the target is vulnerable. The repository is structured simply, with a single Java exploit file and a brief README. No detection scripts or framework integration are present; this is a standalone POC exploit.
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 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.