CVE-2019-2618 is a vulnerability in the WLS Core Components of Oracle WebLogic Server, affecting versions 10.3.6.0.0, 12.1.3.0.0, and 12.2.1.3.0. The vulnerability allows a high-privileged attacker with network access via HTTP to gain unauthorized access to critical data or perform unauthorized data modifications. The vulnerability is easily exploitable and does not require user interaction.
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 a working exploit for CVE-2019-2618, a vulnerability in Oracle WebLogic Server's deployment service. The exploit is implemented in Python (cve-2019-2618.py) and requires valid WebLogic credentials. It crafts a multipart/form-data POST request to the /bea_wls_deployment_internal/DeploymentService endpoint, uploading a JSP webshell (shell.jsp) to the server. The webshell allows remote command execution via HTTP requests. The README.md provides usage instructions, example credentials, and details on relevant file paths for credential extraction and shell upload locations. The exploit is operational, providing a real webshell payload, and targets Oracle WebLogic Server 10.3.6.0. The main attack vector is network-based, requiring access to the vulnerable deployment endpoint. Several fingerprintable endpoints and file paths are documented, including the deployment service URL, webshell location, and files used for credential extraction.
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.