CVE-2020-14527
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 · uneditedVulnerability in the Primavera Portfolio Management product of Oracle Construction and Engineering (component: Web Access). Supported versions that are affected are 16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0 and 19.0.0.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Primavera Portfolio Management. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Primavera Portfolio Management accessible data as well as unauthorized update, insert or delete access to some of Primavera Portfolio Management accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 confidenceUnauthenticated HTTP vulnerability in Primavera Portfolio Management Web Access component allows remote attackers to gain unauthorized access to critical data and perform unauthorized updates/inserts/deletes. Exploitation requires human interaction (making it difficult) but no authentication. High confidentiality impact with low integrity impact.
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>= 16.1.0.0, <= 16.1.5.1>= 18.0.0.0, <= 18.0.2.0= 19.0.0.0CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Primavera Portfolio Management versionLocate the installation directory and check version files (such as version.info, about screen in the application, or check the Oracle installer logs). Alternatively, check the application's help/about section if accessible via the web interface.Affected if The installed version falls within 16.1.0.0-16.1.5.1, 18.0.0.0-18.2.0.0, or equals 19.0.0.0.
-
Confirm Web Access component is exposedDetermine if the web access component (HTTP/HTTPS listeners) is enabled and accessible from the network. Check the application server configuration (typically in the application's configuration files or the underlying application server settings).Affected if The web access component is enabled and reachable over HTTP or HTTPS from network locations.
-
Check for unauthenticated access to sensitive endpointsReview HTTP access logs for the Primavera Portfolio Management application for requests to sensitive data endpoints that occur without prior authentication (look for requests to data retrieval or modification URLs without session tokens).Affected if There are HTTP requests to critical data endpoints that return sensitive information or allow modifications without authentication credentials.
-
Verify network exposureReview firewall rules, network ACLs, or web proxy configurations that control access to the Primavera Portfolio Management web interface.Affected if The web access component is open to untrusted network segments or the internet without proper access restrictions.
A user is affected if their installed Primavera Portfolio Management version is within 16.1.0.0-16.1.5.1, 18.0.0.0-18.2.0.0, or 19.0.0.0, and the Web Access component is network-accessible without authentication filters.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update for CVE-2020-14527; until patched, restrict network access to Primavera Portfolio Management to trusted sources only.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14527 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14527 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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