CVE-2020-14528
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. Easily exploitable 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 and while the vulnerability is in Primavera 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 Portfolio Management accessible data as well as unauthorized read access to a subset of Primavera Portfolio Management accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/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 confidenceOracle Primavera Portfolio Management Web Access component contains an unauthenticated vulnerability exploitable via HTTP. Attackers require human interaction (e.g., tricking a user into clicking a malicious link) and can achieve unauthorized read and delete access to a subset of accessible data. The scope change indicates potential impact to additional products beyond the vulnerable component.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Primavera Portfolio Management installationLook for the product installation directory (commonly in C:\Oracle\Primavera\PortfolioManagement or /Oracle/Primavera/PortfolioManagement on Unix). Check for the 'ppm' service or process running on the server.Affected if The product is installed on the system.
-
Determine the installed versionCheck the version file in the installation directory, typically found in a 'version.properties' or 'build.info' file within the main installation folder. You can also access the web login page and look for an 'About' or version information link.Affected if The installed version falls within 16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0, or equals 19.0.0.0.
-
Verify web access component is enabledCheck if the HTTP/HTTPS web interface is running. Look for the application server (typically Oracle WebLogic or similar) hosting the Portfolio Management web application. Verify the web port is open and responding (default ports often 8080, 8443, or 80/443).Affected if The web access component is exposed and accessible via HTTP/HTTPS.
-
Confirm network exposureReview firewall rules, load balancer configurations, or reverse proxy settings to determine if the web interface is reachable from outside the internal network or from untrusted users.Affected if The web interface is accessible from untrusted networks without proper authentication barriers.
You are affected if Oracle Primavera Portfolio Management is installed with a version between 16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0, or exactly 19.0.0.0, AND the web access component is accessible via HTTP/HTTPS.
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 Updates for the affected versions (16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0, 19.0.0.0). Consider deploying a WAF with appropriate rules and implementing network segmentation to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2020-14528 — 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-14528 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