Loading vulnerability…
CVE-2018-3245 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 port to remotely compromise the server. The vulnerability is easily exploitable and can lead to full takeover of the affected WebLogic Server instance.
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 (3 hidden).
This repository provides an operational exploit for CVE-2018-3245, a remote code execution vulnerability in Oracle WebLogic Server. The exploit consists of a Python script (weblogic.py) and a README.md with usage instructions. The attack requires generating a malicious serialized Java payload using an external tool (ysoserial-cve-2018-3245.jar), which is then sent to the target WebLogic server's T3 protocol port (default 7001) via the Python script. The script establishes a TCP connection, sends a crafted T3 protocol header, and delivers the serialized payload, potentially resulting in arbitrary command execution on the server. The repository is structured simply, with the Python script as the main exploit and the README providing clear, step-by-step instructions. The exploit targets Oracle WebLogic Server instances vulnerable to CVE-2018-3245 and requires network access to the T3 service.
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.