dbcve.org
Weblogic ServerApplication · Oracle

CVE-2020-2867

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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 Container). Supported versions that are affected are 12.1.3.0.0, 12.2.1.3.0 and 12.2.1.4.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 unauthorized creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data as well as unauthorized read access to a subset of Oracle WebLogic Server accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 · moderate confidence

Unauthenticated remote vulnerability in Oracle WebLogic Server's Web Container component allows attackers with network access via HTTP to create, delete or modify critical data as well as read a subset of accessible data. The high integrity impact (I:H) with low confidentiality impact (C:L) indicates the vulnerability primarily enables unauthorized data modification rather than data exfiltration.

MitigationApply Oracle's quarterly security patches for the affected WebLogic Server versions (12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0). As an immediate workaround, restrict network access to WebLogic admin interfaces and implement WAF rules to filter malicious HTTP requests.

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:= 12.1.3.0.0= 12.2.1.3.0= 12.2.1.4.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
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 version
    Run the command 'java -jar $ORACLE_HOME/wlserver_12.1/server/lib/weblogic.jar' or check the installation directory for version files. You can also query the admin console or use WLST: 'java weblogic.WLST' then 'connect()' and 'java.sql.Timestamp(System.getProperty("java.class.version"))' or check the About page in the admin console.
    Affected if The installed version matches exactly 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0
  2. Confirm Web Container is HTTP-accessible
    Verify that the WebLogic HTTP listener is enabled and bound to a network interface. Check the Admin Console under Servers > YourServer > General > Listen Port (usually 7001 for admin, or 80/8080 for managed servers). Confirm the Listen Port Enabled checkbox is checked.
    Affected if HTTP listeners are enabled and the Web Container is reachable over HTTP on any accessible port
  3. Verify network exposure of WebLogic interfaces
    Review firewall rules and network configuration to determine if the WebLogic admin console or T3/IIOP ports are exposed to untrusted networks. Use 'netstat -an | grep 7001' or similar to list listening interfaces.
    Affected if The WebLogic HTTP port (typically 7001, 7002, or custom ports) is bound to 0.0.0.0 or an IP accessible from untrusted networks
  4. Inspect HTTP access logs for suspicious patterns
    Examine WebLogic access logs in $ORACLE_HOME/user_projects/domains/YourDomain/servers/YourServer/logs/access.log for unusual POST requests, especially to the Web Container endpoints. Look for repeated requests from single sources targeting sensitive operations.
    Affected if Logs show unexpected or unauthorized HTTP requests to Web Container endpoints, particularly POST or PUT methods to sensitive data paths

You are affected if your Oracle WebLogic Server is version 12.1.3.0.0, 12.2.1.3.0, or 12.2.1.4.0 and the Web Container HTTP interface is accessible over the network.

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's quarterly security patches for the affected WebLogic Server versions (12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0). As an immediate workaround, restrict network access to WebLogic admin interfaces and implement WAF rules to filter malicious HTTP requests.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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