dbcve.org
KnowledgeWeb browser · Oracle

CVE-2020-2931

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 8.6.3 or later.
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 Knowledge product of Oracle Knowledge (component: Web Applications - InfoCenter). Supported versions that are affected are 8.6.0-8.6.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Knowledge. Successful attacks of this vulnerability can result in takeover of Oracle Knowledge. CVSS 3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/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 · moderate confidence

Unauthenticated remote code execution vulnerability in Oracle Knowledge's InfoCenter web application component. Attackers can exploit this via HTTP requests without credentials to achieve complete system compromise, including confidentiality, integrity, and availability impacts.

MitigationApply Oracle Critical Patch Update or upgrade Oracle Knowledge to a version beyond 8.6.3. If immediate patching is not feasible, restrict network access to InfoCenter endpoints via firewall or WAF rules.

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
KnowledgeWeb browser
Affected:>= 8.6.0, <= 8.6.3

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 Oracle Knowledge installation
    Locate the Oracle Knowledge installation directory or running processes. Check for the InfoCenter web application component typically deployed on application servers (WebLogic, etc.)
    Affected if Oracle Knowledge software is present on the system
  2. Determine installed Oracle Knowledge version
    Locate version files or check product documentation for the installed version number. Common locations include installation logs, version.properties files, or the administration console.
    Affected if Installed version is between 8.6.0 and 8.6.3 inclusive
  3. Verify InfoCenter component exposure
    Determine if the InfoCenter web application is accessible via HTTP/HTTPS. Check application server deployments and network accessible URLs for InfoCenter endpoints.
    Affected if InfoCenter web application is network-accessible without authentication

System is affected if Oracle Knowledge version 8.6.0 through 8.6.3 is installed with the InfoCenter component exposed to network access.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.6.3
Interim mitigation

Apply Oracle Critical Patch Update or upgrade Oracle Knowledge to a version beyond 8.6.3. If immediate patching is not feasible, restrict network access to InfoCenter endpoints via firewall or WAF rules.

Recommended fix Moderate confidence
  1. Apply the latest Oracle Critical Patch Update (CPU) that includes the fix for CVE-2020-2931. Oracle CPUs are released quarterly and available from oracle.com/security-alerts or through Oracle Support.
  2. Verify the patch addresses Oracle Knowledge version 8.6.x by reviewing the CPU advisory for this specific CVE.
  3. After applying the patch, restart Oracle Knowledge services as directed by the patch documentation.
  4. Validate the fix by confirming the InfoCenter component responds correctly and reviewing system logs for any security-related events.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Knowledge Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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