CVE-2020-14529
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: Investor Module). 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 low privileged 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 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · moderate confidenceVulnerability in Oracle Primavera Portfolio Management's Investor Module allows low-privileged authenticated attackers with network access to perform unauthorized read, insert, update, and delete operations on accessible data. The exploit requires human interaction and may impact additional products in the scope. Likely an injection vulnerability given the data manipulation capabilities.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Oracle Primavera Portfolio Management software on the system, typically installed in Oracle WebLogic or similar application server directories. Check program files or application server deploy directories for 'Primavera' or 'Portfolio Management' components.Affected if The software is not installed or is a different product entirely.
-
Determine installed version numberCheck the installed version of Oracle Primavera Portfolio Management. This is typically found in the application server admin console, the software's About/Version info, or in configuration files within the installation directory. Compare the version to the affected ranges: 16.1.0.0 through 16.1.5.1, 18.0.0.0 through 18.0.2.0, or 19.0.0.0.Affected if The installed version falls within any of the affected version ranges.
-
Verify Investor Module is enabledAccess the Oracle Primavera Portfolio Management admin interface or configuration settings. Check whether the Investor Module component is enabled and accessible to users.Affected if The Investor Module is enabled and accessible to authenticated users.
-
Check network accessibility of Investor ModuleReview network access controls, firewall rules, and application access policies that govern who can reach the Investor Module over the network. Determine if untrusted network paths exist to this module.Affected if The Investor Module is network-accessible to users outside trusted boundaries.
A user is affected if Oracle Primavera Portfolio Management is installed with a version in the ranges 16.1.0.0-16.1.5.1, 18.0.0.0-18.0.2.0, or 19.0.0.0 AND the Investor Module is enabled and network-accessible to the attacker.
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 quarterly security patches for Primavera Portfolio Management. Until patches are applied, restrict network access to the Investor Module to trusted users only and monitor for suspicious data access patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14529 — 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-14529 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