dbcve.org
Primavera P6 Enterprise Project Portfolio ManagementApplication · Oracle

CVE-2024-21095

HIGH · 8.2 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 23.12.2 or later.
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 Primavera P6 Enterprise Project Portfolio Management product of Oracle Construction and Engineering (component: Web Access). Supported versions that are affected are 19.12.0-19.12.22, 20.12.0-20.12.21, 21.12.0-21.12.18, 22.12.0-22.12.12 and 23.12.0-23.12.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Primavera P6 Enterprise Project Portfolio Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Primavera P6 Enterprise Project Portfolio Management accessible data as well as unauthorized update, insert or delete access to some of Primavera P6 Enterprise Project Portfolio Management accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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

Unauthenticated remote vulnerability in the Web Access component of Oracle Primavera P6 Enterprise Project Portfolio Management allows unauthenticated attackers with network access via HTTP to compromise the system. Successful exploitation grants unauthorized access to critical project data and potentially insert, update, or delete access to some data due to missing or inadequate authentication controls in the web interface.

MitigationApply Oracle's critical patch updates for Primavera P6 (versions 19.12 through 23.12) as listed in Oracle's April 2024 Critical Patch Update. Implement network segmentation and WAF rules as interim controls until patches can be applied.

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:>= 19.12.0, <= 19.12.22>= 20.12.0, <= 20.12.21>= 21.12.0.0, <= 21.12.18>= 22.12.0, <= 22.12.12>= 23.12.0, <= 23.12.2

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 P6 installed version
    Log into the P6 administration console or check the P6 installer/About section. On the server, examine the P6 installation directory for version files or run: java -jar p6version.jar or check the Oracle inventory file. Alternatively, access the login page footer which often displays the version.
    Affected if The displayed version falls within these ranges: 19.12.0-19.12.22, 20.12.0-20.12.21, 21.12.0.0-21.12.18, 22.12.0-22.12.12, or 23.12.0-23.12.2
  2. Confirm Web Access component is enabled
    Check the P6 configuration for the Web Access (P6 Web) service. Typically located in the P6 admin settings or by examining the deployed web application files under the application server webapps directory (e.g., $ORACLE_HOME/user_projects/domains/.../p6). Verify the p6web.war or p6 application is deployed and running.
    Affected if The Web Access component is deployed and running, exposing the P6 web interface on HTTP/HTTPS ports (typically 8080, 8443, or the configured web server ports)
  3. Verify network accessibility of the Web Access interface
    From an external host, attempt to reach the P6 Web URL: http(s)://<server>:<port>/p6. Use a browser or curl command: curl -I http://<target>:<port>/p6. Check firewall rules and load balancer configurations to determine if the interface is accessible from untrusted networks.
    Affected if The Web Access URL is reachable from a network where untrusted or anonymous attackers could send HTTP requests to the p6 endpoint
  4. Check for missing authentication enforcement
    Attempt to access P6 resources without providing credentials. Browse to common P6 API endpoints such as /p6/rest/services or /p6/api without a login session. Inspect whether the server returns project data, configuration details, or allows unauthenticated API calls.
    Affected if The server returns project data, user information, or permits access to API endpoints without requiring authentication credentials

If the installed P6 version falls within any of the affected ranges AND the Web Access component is exposed and accessible over the network, the environment is vulnerable to unauthenticated remote compromise via CVE-2024-21095.

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 23.12.2
Interim mitigation

Apply Oracle's critical patch updates for Primavera P6 (versions 19.12 through 23.12) as listed in Oracle's April 2024 Critical Patch Update. Implement network segmentation and WAF rules as interim controls until patches can be applied.

Recommended fix High confidence

Upgrade to the next available patch set within your current major version line (e.g., 19.12.23+, 20.12.22+, 21.12.19+, 22.12.13+, 23.12.3+)

  1. Check Oracle's official support portal (.oracle.com) for the April 2024 Critical Patch Update (CPU) or subsequent updates that address CVE-2024-21095
  2. Identify your current Primavera P6 EPPM version from the Admin menu > About Primavera P6
  3. For 19.12.x versions: Upgrade to version 19.12.23 or later
  4. For 20.12.x versions: Upgrade to version 20.12.22 or later
  5. For 21.12.x versions: Upgrade to version 21.12.19 or later
  6. For 22.12.x versions: Upgrade to version 22.12.13 or later
  7. For 23.12.x versions: Upgrade to version 23.12.3 or later
  8. After upgrade, verify the patch level matches the fixed version via Admin > About
Caveat Standard Oracle patch upgrades typically preserve data and configuration; however, always backup the database and test in staging before production deployment

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

Fix this in Primavera P6 Enterprise Project Portfolio Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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