CVE-2024-21182
Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability is exploited via T3 and IIOP protocols, which are not HTTP-based and thus not filterable by a web application firewall. The attack uses network access through these protocols, so a WAF cannot block it.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-21182 being exploited?
Yes. CVE-2024-21182 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-21182?
CVE-2024-21182 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-21182?
Yes. A fix has been recorded for CVE-2024-21182. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-21182 affect?
CVE-2024-21182 affects oracle:weblogic_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected12.2.1.4.0
- affected14.1.1.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 4 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 2 Jan 2025 (SSVC 2.0.3).
timeline
- 16 Jul 2024Published
- 29 Dec 2024First proof-of-concept repository on GitHub (unvetted) · 165 days (about 6 months) later
- 2 Jan 2025CISA SSVC assessment: exploitation active · 4 days later
- 1 Jun 2026Added to CISA KEV (exploited in the wild) · 515 days (about 1 year) later
- 2 Jun 2026CVE record last updated · 1 day later
- 4 Jun 2026CISA remediation due date (US federal agencies) · 2 days later
- 2 Nov 2026Analysed by vulneraibility.com · 152 days (about 5 months) later
- Advisoryoracle.com /security-alerts/cpujul2024.html
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-21182
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.