dbcve.org
Primavera P6 Enterprise Project Portfolio ManagementApplication · Oracle

CVE-2017-3324

CRITICAL · 10.0 CVSS v3.0 Published 2017-01-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 component of Oracle Primavera Products Suite (subcomponent: Web Access). Supported versions that are affected are 8.2, 8.3, 8.4, 15.1, 15.2, 16.1 and 16.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Primavera P6 Enterprise Project Portfolio Management. 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 creation, deletion or modification access to critical data or all Primavera P6 Enterprise Project Portfolio Management accessible data as well as unauthorized access to critical data or complete access to all 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 v3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts).

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 Primavera P6 Enterprise Project Portfolio Management's Web Access component allows attackers via HTTP to create, delete, or modify critical data, gain full unauthorized access to all accessible data, and cause partial denial of service. The CVSS 10.0 score indicates trivial exploitability with complete compromise of confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update that addresses CVE-2017-3324; if immediate patching is not possible, restrict network access to the Web Access interface via firewall or VPN until the patch can be deployed.

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:= 8.2= 8.3= 8.4= 15.1= 15.2= 16.1= 16.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
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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. Confirm Oracle Primavera P6 EPPM installation
    Locate the Primavera P6 installation directory or check for the p6 web application (.war file or exploded directory) on the application server. Look for folders named 'p6' or 'primavera' in the application server's webapps or deploy directory.
    Affected if Primavera P6 EPPM is installed and the Web Access component is deployed
  2. Identify installed P6 version
    Check the version of the installed Primavera P6 EPPM. This can typically be found in a version.properties file within the p6 web application directory, or by accessing the P6 Web Access login page and viewing the footer/version information.
    Affected if The installed version matches 8.2, 8.3, 8.4, 15.1, 15.2, 16.1, or 16.2
  3. Verify Web Access component is enabled
    Confirm that the P6 Web Access (p6/ppm) web application is deployed and running on the application server. Check if the Web Access endpoint is accessible via HTTP/HTTPS (typically at paths like /p6 or /ppm).
    Affected if The Web Access component is deployed and accessible via HTTP
  4. Check network accessibility of Web Access
    Determine if the Web Access interface is exposed to untrusted networks. Review firewall rules, load balancer configurations, or reverse proxy settings that control access to the P6 Web Access URL. Test access from an untrusted network perspective if possible.
    Affected if The Web Access interface is reachable from untrusted or external networks without proper access controls

If Primavera P6 EPPM versions 8.2 through 16.2 are installed with the Web Access component exposed to the network, the environment is affected by CVE-2017-3324.

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply Oracle Critical Patch Update that addresses CVE-2017-3324; if immediate patching is not possible, restrict network access to the Web Access interface via firewall or VPN until the patch can be deployed.

Recommended fix Moderate confidence

Upgrade to a version beyond 16.2 (contact Oracle for current supported versions)

  1. Navigate to the Oracle Critical Patch Update January 2017 advisory at http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html
  2. Locate the patch for Primavera P6 Enterprise Project Portfolio Management (CVE-2017-3324)
  3. Download and apply the applicable patch for your specific version (8.2, 8.3, 8.4, 15.1, 15.2, 16.1, or 16.2) from My Oracle Support
  4. Apply the patch according to Oracle's installation instructions for your platform
  5. Restart affected P6 services to ensure the patch takes effect
  6. Verify the patch was applied successfully by confirming the vulnerability is resolved
Caveat Patches may require downtime; test in non-production environment before applying to production

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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