Primavera P6 Enterprise Project Portfolio ManagementApplication · Oracle

CVE-2020-2594

MEDIUM · 6.5 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 20.2.0.0 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 Primavera P6 Enterprise Project Portfolio Management product of Oracle Construction and Engineering (component: Project Manager). Supported versions that are affected are 16.2.0.0 - 16.2.19.3, 17.12.0.0 - 17.12.17.0, 18.8.0.0 - 18.8.18.0, 19.12.1.0 - 19.12.3.0 and 20.1.0.0 - 20.2.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Primavera P6 Enterprise Project Portfolio Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Primavera P6 Enterprise Project Portfolio Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Primavera P6 Enterprise Project Portfolio Management accessible data as well as unauthorized read access to a subset of Primavera P6 Enterprise Project Portfolio Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Primavera P6 Enterprise Project Portfolio Management. CVSS 3.0 Base Score 6.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L).

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 Primavera P6 Enterprise Project Portfolio Management contains a vulnerability in the Project Manager component that allows low-privileged attackers with network access via HTTP to achieve unauthorized read, insert, update, and delete access to a subset of application data, plus partial denial of service. The attack requires human interaction and targets specific data within the Project Manager functionality.

MitigationApply Oracle Critical Patch Update (CPU) patches for CVE-2020-2594 or upgrade to a fixed version outside the affected version ranges (16.2.x, 17.12.x, 18.8.x, 19.12.x, 20.1-20.2).

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
Primavera P6 Enterprise Project Portfolio ManagementApplication
Affected:>= 16.2.0.0, <= 16.2.19.3>= 17.12.0.0, <= 17.12.17.0>= 18.8.0.0, <= 18.8.18.0>= 19.12.1.0, <= 19.12.3.0>= 20.1.0.0, <= 20.2.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Primavera P6 installation and version
    Locate the Primavera P6 installation directory or access the application About/Admin pages to retrieve the exact version number
    Affected if The installed version falls within any of these ranges: 16.2.0.0-16.2.19.3, 17.12.0.0-17.12.17.0, 18.8.0.0-18.8.18.0, 19.12.1.0-19.12.3.0, or 20.1.0.0-20.2.0.0
  2. Confirm Project Manager component is in use
    Verify that the Project Manager module is enabled and accessible within the Primavera P6 deployment
    Affected if The Project Manager functionality is active and available to users
  3. Verify HTTP network accessibility
    Check if the P6 application is exposed over HTTP/HTTPS network access, as this vulnerability is exploitable remotely via HTTP
    Affected if The application is reachable over network with HTTP protocol
  4. Check for low-privileged user accounts
    Review user accounts in the P6 administrator console to confirm presence of low-privileged accounts that could potentially exploit this flaw
    Affected if Low-privileged user accounts exist in the system who could potentially exploit the unauthorized data access vector

The environment is affected if Oracle Primavera P6 EPPM is installed with a version matching the affected ranges and the Project Manager component is accessible to low-privileged users 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
Upgrade available Upgrade to a release after 20.2.0.0
Interim mitigation

Apply Oracle Critical Patch Update (CPU) patches for CVE-2020-2594 or upgrade to a fixed version outside the affected version ranges (16.2.x, 17.12.x, 18.8.x, 19.12.x, 20.1-20.2).

Fix this in Primavera P6 Enterprise Project Portfolio Management 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-2594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2594 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