CVE-2020-14549
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 Server). 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 HTTPS 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 confidenceVulnerability in the Web Server component of Oracle Primavera Portfolio Management. This is a difficult-to-exploit, pre-authentication flaw allowing unauthenticated network attackers to gain unauthorized access to critical data and limited update/insert/delete capabilities, but requires human interaction (e.g., tricking a user into visiting a malicious link).
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.
-
Confirm Oracle Primavera Portfolio Management is installedLocate the Primavera Portfolio Management installation directory or check for the application in your system inventory. Common locations include C:\Program Files\Oracle\Primavera Portfolio Management or /opt/oracle/primavera/portfolio on Linux.Affected if The product is not installed - no action needed. If installed, proceed to version check.
-
Determine the installed versionCheck the version of Primavera Portfolio Management. Typically found in an about page, version.info file, or the administration console. The version format follows the pattern X.X.X.X (e.g., 16.1.0.0, 18.0.0.0, 19.0.0.0).Affected if Version falls within: 16.1.0.0 through 16.1.5.1, OR 18.0.0.0 through 18.0.2.0, OR exactly 19.0.0.0. If version is outside these ranges, the system may not be affected.
-
Verify the Web Server component is enabledConfirm that the Web Server component for Primavera Portfolio Management is running. Check the application services console or use commands like 'services.msc' on Windows or 'systemctl status' on Linux to verify the web server service is active.Affected if The web server component is running and accessible - this is required for the vulnerability to be exploitable.
-
Check network exposure of the web interfaceDetermine if the web server interface is accessible over the network. Review firewall rules, load balancer configurations, or network ACLs. Verify whether the HTTP/HTTPS ports (commonly 8080, 8443, or standard web ports) are exposed to untrusted networks.Affected if The web interface is accessible from untrusted networks or the internet - this increases exposure to unauthenticated attackers.
The environment is affected if Oracle Primavera Portfolio Management is installed with a version matching 16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0, or 19.0.0.0, and the Web Server component is running and network-accessible to attackers.
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's applicable security patches for Primavera Portfolio Management. If patches cannot be applied immediately, restrict network access to the web server interface to reduce exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14549 — 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-14549 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