dbcve.org
Enterprise RepositoryApplication · Oracle

CVE-2021-1994

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Web Services). Supported versions that are affected are 10.3.6.0.0 and 12.1.3.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated remote code execution vulnerability in Oracle WebLogic Server's Web Services component. An attacker with network access via HTTP can exploit this to gain complete control of the WebLogic Server, achieving full confidentiality, integrity, and availability compromise.

MitigationApply Oracle Critical Patch Update (CPU) for January 2021 which contains the security fix for this vulnerability. If immediate patching is not feasible, consider restricting network access to WebLogic Server endpoints or disabling affected web services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise RepositoryApplication
Affected:= 11.1.1.7.0
Weblogic ServerApplication
Affected:= 10.3.6.0.0= 12.1.3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle WebLogic Server is installed
    Check for WebLogic installation directories (typically $ORACLE_HOME/wlserver or $MW_HOME/wlserver) and look for the file 'registry.xml' or use the WebLogic Administration Console (typically at port 7001 by default). Alternatively, search for 'weblogic.jar' in common paths like /oracle/wlserver or C:\oracle\wlserver.
    Affected if WebLogic Server version 10.3.6.0.0 or 12.1.3.0.0 is found installed
  2. Identify if Oracle Enterprise Repository is installed
    Check for Oracle Enterprise Repository installation directories (typically under $ORACLE_HOME/Oracle_EPR) and look for version information in installation manifests or the file 'registry.xml' located in the installation root.
    Affected if Oracle Enterprise Repository version 11.1.1.7.0 is found installed
  3. Confirm the Web Services component is configured
    Access the WebLogic Administration Console and navigate to 'Domain' > 'Environment' > 'Deployments' to list all deployed applications. Look for web service applications (WSD or JAX-WS based) or check for WSDL endpoints exposed on the HTTP port (typically /wls_uds or /_async/AsyncResponseService).
    Affected if Web Services are deployed and exposed via HTTP on the WebLogic server (the vulnerability requires the Web Services component to be accessible)
  4. Verify network accessibility of WebLogic HTTP ports
    Check if WebLogic HTTP ports (default 7001, or custom ports configured) are exposed to untrusted networks. Use 'netstat -an | grep LISTEN' on the server or perform an external port scan to determine if HTTP (port 80/443/7001/8001) is listening on interfaces accessible from outside.
    Affected if WebLogic HTTP ports are listening on externally accessible network interfaces (the vulnerability can only be exploited by attackers with network access via HTTP)

A user is affected if they have WebLogic Server 10.3.6.0.0 or 12.1.3.0.0, or Oracle Enterprise Repository 11.1.1.7.0, with Web Services enabled and exposed via HTTP on a network-accessible port.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for January 2021 which contains the security fix for this vulnerability. If immediate patching is not feasible, consider restricting network access to WebLogic Server endpoints or disabling affected web services.

Fix this in Enterprise Repository Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1994 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data