dbcve.org
Primavera Portfolio ManagementApplication · Oracle

CVE-2022-21377

MEDIUM · 5.4 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 19.0.1.2 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Portfolio Management product of Oracle Construction and Engineering (component: Web API). Supported versions that are affected are 18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2 and 20.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. 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:N/UI:R/S:U/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 confidence

Unauthenticated HTTP API vulnerability in Oracle Primavera Portfolio Management Web API component allows unauthenticated attackers with network access to read and modify a subset of accessible data. Exploitation requires victim user interaction (e.g., clicking a malicious link). Affects versions 18.x, 19.x, and 20.x.

MitigationApply Oracle Critical Patch Update (CPU) for January 2022 or later that addresses CVE-2022-21377. If immediate patching is not feasible, restrict network access to the Web API and implement WAF rules to detect/block anomalous API requests.

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 Portfolio ManagementApplication
Affected:>= 18.0.0.0, <= 18.0.3.0>= 19.0.0.0, <= 19.0.1.2= 20.0.0.0

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle Primavera Portfolio Management is installed
    Check the application inventory or installed programs list for 'Oracle Primavera Portfolio Management' or 'Primavera Portfolio Management'
    Affected if The product is not present in the environment, the user is not affected
  2. Determine the installed version of Primavera Portfolio Management
    Locate the version information in the product's about dialog, installation directory, or admin console. Common locations include the installation folder or the application's help/about section
    Affected if The installed version falls within 18.0.0.0 through 18.0.3.0, 19.0.0.0 through 19.0.1.2, or is exactly 20.0.0.0
  3. Verify the Web API component is accessible
    Check if the Web API endpoint is exposed by attempting to access the API URL (typically at /api/ or /webapi/ paths on the application's web server) from a network location
    Affected if The Web API is reachable from the network without authentication, the user may be affected
  4. Confirm network accessibility to unauthenticated attackers
    Review firewall rules, network segmentation, and access control lists to determine if the Web API is accessible to unauthenticated network attackers
    Affected if The Web API is accessible to unauthenticated users on the network, exploitation is possible

The user is affected if Oracle Primavera Portfolio Management versions 18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2, or 20.0.0.0 are installed with the Web API exposed to unauthenticated network access.

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
Upgrade available Upgrade to a release after 19.0.1.2
Interim mitigation

Apply Oracle Critical Patch Update (CPU) for January 2022 or later that addresses CVE-2022-21377. If immediate patching is not feasible, restrict network access to the Web API and implement WAF rules to detect/block anomalous API requests.

Recommended fix Moderate confidence

Oracle Critical Patch Update January 2022 (contact Oracle for exact version numbers per release train)

  1. 1. Navigate to Oracle Support (support.oracle.com) and search for patch information on CVE-2022-21377
  2. 2. Download the applicable patch for your installed version of Primavera Portfolio Management
  3. 3. Apply the patch following Oracle's standard patch application procedures for Primavera products
  4. 4. Verify the patch was applied successfully by checking the version number and testing the Web API functionality
  5. 5. Confirm the vulnerability is resolved by reviewing the Oracle Critical Patch Update documentation for January 2022

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Primavera 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 upgrade done

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-2022-21377 — 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-2022-21377 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