Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Oracle WebLogic Server Core Unspecified Vulnerability via T3/IIOP

IdentifiersCVE-2024-21182

CVE-2024-21182 is an unspecified vulnerability in the Core component of Oracle WebLogic Server affecting supported versions 12.2.1.4.0 and 14.1.1.0.0. Oracle describes it as easily exploitable by an unauthenticated attacker with network access to the target over the T3 or IIOP protocols. Publicly provided technical details in the supplied content do not identify the exact vulnerable function or root cause, but successful exploitation can compromise the WebLogic instance and expose data accessible through the server. The vulnerability was patched by Oracle in the July 2024 Critical Patch Update and has since been added by CISA to the Known Exploited Vulnerabilities catalog based on evidence of active exploitation.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in unauthorized access to critical data or complete access to all data accessible by the affected Oracle WebLogic Server instance. Based on the supplied Oracle and CISA descriptions, the primary demonstrated impact is high confidentiality loss rather than integrity or availability impact, consistent with the provided CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N and base score 7.5.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, restrict or disable exposure of the T3 and IIOP protocols to untrusted networks, especially the public internet, using firewall rules, ACLs, segmentation, or listener configuration changes where operationally feasible. Limit access to WebLogic services to trusted administrative or application peers only. Oracle notes that protocol-blocking workarounds may affect application functionality and should be validated before production deployment. These measures are temporary risk reductions and not substitutes for applying the vendor patch.

Remediation

Patch, then assume compromise.

Apply Oracle’s July 2024 Critical Patch Update or later vendor-provided security update that addresses CVE-2024-21182. Organizations should ensure affected Oracle WebLogic Server deployments on versions 12.2.1.4.0 and 14.1.1.0.0 are updated to a fixed supported release in accordance with Oracle guidance. If patching has been deferred, review Oracle CPU prerequisites and any skipped prior updates to ensure the remediation fully covers the vulnerable installation.
PUBLIC EXPLOITS

Exploits

3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 3 / 3 TOTALView more in app
CVE-2024-21182MaturityPoCVerified exploit

This repository is a self-contained lab exploit for Oracle WebLogic Server CVE-2024-21182, described as an unauthenticated T3/IIOP JNDI injection leading to server-side LDAP lookup and, in the provided lab conditions, remote code execution. The repo is not tied to a common exploit framework; it contains custom Java, Python, Bash, and Docker components. Structure and purpose: - poc/CVE_2024_21182.java is the main exploit client. It connects to a WebLogic T3 endpoint, constructs a malicious weblogic.application.naming.MessageDestinationReference, reflectively inserts it into an AggregatableOpaqueReference, binds it into JNDI, and triggers lookup() so the server performs an attacker-controlled LDAP lookup. - exploit/ldap_server.py is the attacker infrastructure. It implements a minimal LDAP server that answers searches with a javaNamingReference containing javaClassName=Exploit, javaFactory=Exploit, and javaCodeBase pointing to an HTTP server. The same script also starts an HTTP server to host the compiled class file. - exploit/Exploit.java is the payload class. Its static initializer executes /bin/sh -c 'id ...; uname -a ...' and writes output to /tmp/RCE_PROOF_CVE_2024_21182 on the victim. - exploit/build.sh recompiles Exploit.java to Java 8 bytecode for compatibility with the lab’s older JDK. - docker-compose.yml provisions a vulnerable WebLogic container and an attacker container exposing the LDAP/HTTP services. - validate.sh automates end-to-end reproduction: waits for WebLogic readiness, copies and compiles the PoC inside the container against the live WebLogic classpath, runs the exploit against 127.0.0.1:7001 with ldap://attacker:1389/Evil, and checks for the proof file. Main exploit capability: The exploit provides unauthenticated network-triggered JNDI injection over T3, causing the target WebLogic server to initiate outbound LDAP and HTTP connections to attacker-controlled infrastructure. In the included lab, this results in arbitrary command execution via remote Java class loading. On newer JDKs or patched systems, the same technique may degrade to SSRF/outbound lookup without RCE. Notable targeting details: The README states Oracle WebLogic Server 12.2.1.4.0 and 14.1.1.0.0 are the CVE-listed affected versions, while the lab uses vulhub/weblogic:12.2.1.3-2018 to reproduce the vulnerable class behavior. The exploit specifically abuses WebLogic classes AggregatableOpaqueReference and MessageDestinationReference to bypass prior protections associated with CVE-2023-21839. Overall, this is a real operational lab exploit with a working payload and attacker infrastructure, not merely a detector or README-only proof of concept.

dinosnDisclosed Jun 2, 2026markdownyamlnetworkweb
CVE-2024-21182MaturityPoCVerified exploit

This repository contains a single Java proof-of-concept exploit (CVE_2024_21182.java) targeting Oracle WebLogic Server's JNDI implementation, specifically for CVE-2024-21182. The exploit demonstrates how an attacker can use the T3 protocol to connect to a vulnerable WebLogic server and bind a malicious AggregatableOpaqueReference object containing a MessageDestinationReference that points to an attacker-controlled LDAP server. This could potentially be used to trigger remote code execution or further attacks via JNDI injection. The code is a standalone POC and does not include a full exploit chain or payload delivery, but it clearly demonstrates the vulnerability mechanism. The README is minimal and only states the vulnerability context. The main fingerprintable endpoints are the T3 and LDAP URLs, which are hardcoded as placeholders in the code.

kursadalsanDisclosed Dec 29, 2024javanetwork
CVE-2024-21182MaturityPoCVerified exploit

This repository contains a single Java proof-of-concept exploit for CVE-2024-21182, a JNDI injection vulnerability in Oracle WebLogic Server. The main file, CVE_2024_21182.java, demonstrates how an attacker can use the T3 protocol to connect to a vulnerable WebLogic instance and bind a malicious MessageDestinationReference object that references an attacker-controlled LDAP server. The exploit leverages internal WebLogic classes and Java reflection to craft the payload. The README.md provides a brief description and states the exploit is for educational purposes. The code is a functional POC and does not include a full malicious payload, but it shows the core technique for exploiting the vulnerability. The main network endpoints involved are the target WebLogic server (T3 protocol) and an LDAP server under the attacker's control.

k4it0k1dDisclosed Dec 29, 2024javanetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OracleWeblogic Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

56 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity47

Community discussion across Reddit, Mastodon, and other social sources.