dbcve.org
Agile Product Lifecycle ManagementApplication · Oracle

CVE-2020-2920

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Agile PLM product of Oracle Supply Chain (component: Security). Supported versions that are affected are 9.3.3, 9.3.5 and 9.3.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Agile PLM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Agile PLM, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Agile PLM accessible data as well as unauthorized read access to a subset of Oracle Agile PLM accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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

This is an insecure direct object reference or similar access control vulnerability in the Security component of Oracle Agile PLM versions 9.3.3, 9.3.5, and 9.3.6. An unauthenticated remote attacker can exploit it via HTTP to gain unauthorized read and limited write/delete access to certain PLM data, but the attack requires human interaction from a person other than the attacker.

MitigationApply Oracle's applicable patch for CVE-2020-2920 from the Oracle Critical Patch Updates. If immediate patching is not possible, restrict network access to the Agile PLM HTTP endpoints to trusted sources only.

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
Agile Product Lifecycle ManagementApplication
Affected:= 9.3.3= 9.3.5= 9.3.6

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 if Oracle Agile PLM is installed
    Check for Oracle Agile PLM installation directories (such as $AGILE_HOME or typical Oracle installation paths), or query the system for Agile PLM processes and services.
    Affected if Oracle Agile PLM software is present on the system
  2. Determine the installed Agile PLM version
    Check the version of the Oracle Agile PLM installation. This is typically visible in the application startup logs, the About page of the web client, or version files within the Agile home directory.
    Affected if The installed version is 9.3.3, 9.3.5, or 9.3.6 exactly
  3. Verify the HTTP interface is enabled
    Confirm that the Agile PLM web tier or HTTP server component is running and accessible. Check for HTTP/HTTPS listeners on typical Agile PLM ports (such as 8080, 8443, or configured ports).
    Affected if The web HTTP interface is enabled and listening for connections
  4. Check network accessibility of the HTTP endpoints
    Determine whether the Agile PLM HTTP endpoints are exposed to untrusted networks or the internet. Review firewall rules, load balancer configurations, or reverse proxy settings that control access to the application.
    Affected if The HTTP endpoints are accessible from untrusted network segments or the public internet

A system is affected if Oracle Agile PLM version 9.3.3, 9.3.5, or 9.3.6 is installed with its HTTP interface enabled and accessible from an untrusted 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 applicable patch for CVE-2020-2920 from the Oracle Critical Patch Updates. If immediate patching is not possible, restrict network access to the Agile PLM HTTP endpoints to trusted sources only.

Fix this in Agile Product Lifecycle Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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