Loading vulnerability…
CVE-2018-3252 is a critical vulnerability in Oracle WebLogic Server (versions 10.3.6.0, 12.1.3.0, and 12.2.1.3) within the WLS Core Components. The flaw allows an unauthenticated attacker with network access to the T3 protocol to remotely compromise the server. The vulnerability is easily exploitable and does not require user interaction or authentication, enabling attackers to execute arbitrary code and fully compromise the affected server.
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 (2 hidden).
This repository provides a proof-of-concept (PoC) exploit for CVE-2018-3252, a remote code execution vulnerability in Oracle WebLogic Server. The main code file, PoC.java, generates a malicious serialized Java object (poc4.ser) using gadget chains from the ysoserial project. The payload is designed to execute arbitrary commands (e.g., launching 'calc') on the vulnerable server. The exploit requires valid WebLogic credentials and targets the /bea_wls_deployment_internal/DeploymentService endpoint via an HTTP POST request. The README provides usage instructions and a sample HTTP request. The repository is structured with a single Java exploit file and a markdown README, and is intended for demonstration and testing of the 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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.