CVE-2022-21242
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 18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2, 20.0.0.0 and 20.0.0.1. 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 confidenceA web access vulnerability in Oracle Primavera Portfolio Management allows low-privileged authenticated attackers to perform unauthorized read, insert, update, and delete operations on a subset of accessible data. The CVSS vector indicates network-based attack with low complexity, requiring some human interaction (likely social engineering to lure a user). The impact is primarily on confidentiality and integrity, not availability.
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>= 18.0.0.0, <= 18.0.3.0>= 19.0.0.0, <= 19.0.1.2= 20.0.0.0= 20.0.0.1CVSS 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 installed version of Oracle Primavera Portfolio ManagementLocate the version information in the application's administration console, about page, or installation directory documentation. Common locations include the Oracle Enterprise Manager, the application's help/about section, or the installation logs.Affected if The installed version is 18.0.0.0 through 18.0.3.0, 19.0.0.0 through 19.0.1.2, 20.0.0.0, or 20.0.0.1
-
Confirm web access to Primavera Portfolio Management is enabledVerify that the web-based interface is accessible by attempting to reach the application's URL (typically on ports 8080, 8443, or as configured during installation) from a network location.Affected if The web interface is reachable over the network
-
Verify low-privileged user accounts existCheck the user management section of the application to confirm there are accounts with limited or basic user roles that have any data access permissions.Affected if Low-privileged authenticated users have any data access capabilities
-
Inspect network exposure of the web applicationReview firewall rules, load balancer configurations, or network ACLs to determine if the Primavera Portfolio Management web interface is accessible from untrusted networks.Affected if The application is accessible from networks outside the trusted internal environment, particularly the internet
You are affected if your installed Oracle Primavera Portfolio Management version falls within 18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2, 20.0.0.0, or 20.0.0.1 AND the web interface is accessible to low-privileged authenticated users on your network.
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.
dbcve · scopedApply Oracle's available patches for Primavera Portfolio Management (versions 18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2, 20.0.0.0-20.0.0.1). Until patched, restrict network access to the application and monitor for unusual data access patterns.
Primavera Portfolio Management 18.0.3.1 or later, 19.0.1.3 or later, or 20.0.0.2 or later (or a later supported release)
- Contact Oracle Support or visit the Oracle Critical Patch Update page at https://www.oracle.com/security-alerts/ to obtain the January 2022 Critical Patch Update (CPU) which contains the security fix for this vulnerability.
- Identify the currently installed version of Primavera Portfolio Management using the Oracle administration console or version check utilities.
- Download and apply the appropriate patch from the January 2022 CPU or later that addresses CVE-2022-21242.
- After applying the patch, verify the version has been updated to a version beyond the affected ranges (18.0.3.0, 19.0.1.2, 20.0.0.1).
- Test the application to ensure normal functionality is maintained post-patch.
- Consult Oracle's upgrade documentation for Primavera Portfolio Management to ensure compatibility with your environment.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21242 — 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-2022-21242 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