dbcve.org
Weblogic ServerApplication · Oracle

CVE-2021-1995

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 low privileged attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 6.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).

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

Oracle WebLogic Server contains a vulnerability in its Web Services component (versions 10.3.6.0.0 and 12.1.3.0.0) that allows low-privileged attackers with network access via HTTP to create, delete, or modify critical data. The CVSS vector indicates high integrity impact with no confidentiality or availability impact, and exploitation requires low complexity with low privileges.

MitigationApply the Oracle Critical Patch Update (CPU) that includes the fix for CVE-2021-1995. As a compensating control, restrict network access to WebLogic Server endpoints to trusted sources and follow the principle of least privilege for Web Services permissions.

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
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 WebLogic Server installed version
    Check the version.properties file in the Oracle home directory, typically located at $ORACLE_HOME/wlserver_10.3/integration/shortcuthandlers/version.properties for 10.3.x or look for VERSION.txt in the installation directory. Alternatively, access the WebLogic Administration Console and view the 'About WebLogic Server' information from the 'Help' menu.
    Affected if The installed version matches exactly 10.3.6.0.0 or 12.1.3.0.0
  2. Confirm Web Services component is in use
    Check if Web Services (JAX-WS or JAX-RPC) are deployed by reviewing the WebLogic Administration Console under 'Deployments' > 'Web Services' or by inspecting the config.xml file in the domain config directory for <web-service> or <webservice> deployment entries.
    Affected if Web Services module is deployed and active on the target WebLogic instance
  3. Verify network accessibility to HTTP endpoints
    Confirm that WebLogic HTTP channels are accessible over the network by testing connectivity to the configured HTTP listen port (default 7001 for admin console, or custom ports for managed servers). Use curl or telnet to test: curl -I http://<host>:<port>/<endpoint>
    Affected if HTTP ports are exposed to untrusted networks, allowing remote network access to WebLogic endpoints

You are affected only if your installed WebLogic Server version is exactly 10.3.6.0.0 or 12.1.3.0.0 AND the Web Services component is enabled AND the HTTP endpoint is network-accessible to low-privileged attackers.

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 the Oracle Critical Patch Update (CPU) that includes the fix for CVE-2021-1995. As a compensating control, restrict network access to WebLogic Server endpoints to trusted sources and follow the principle of least privilege for Web Services permissions.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1995 — 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-1995 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