CVE-2022-21269
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 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 confidenceVulnerability in the Web Access component of Oracle Primavera Portfolio Management allows unauthenticated attackers via HTTP to compromise the application. Successful attacks provide unauthorized read access to a subset of data and unauthorized update/insert/delete access to some data. The attack requires human interaction from a victim (likely click or form submission), and while primarily affecting Portfolio Management, it may significantly impact additional products in the Oracle Construction and Engineering suite.
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
- 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.
-
Confirm Primavera Portfolio Management installationLocate the installation directory or check for running services related to 'Primavera' or 'Portfolio Management'. Common paths include Oracle installation directories or WebLogic domains hosting the application.Affected if The product is not installed or the version cannot be determined - if not affected, skip remaining checks.
-
Identify installed versionCheck the application's about page, version info in the administration console, or examine WAR/deployment files in the application server. The web interface typically displays version information at /p6/ or the root URL after login.Affected if Version matches: 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 - proceed to next check.
-
Verify Web Access component is enabledConfirm the web application is deployed and accessible. Check if the HTTP listener on the application's web port (commonly 8080, 8000, or 443/8443 for HTTPS) is responding to requests.Affected if The web interface is accessible via HTTP/HTTPS - this is required for the vulnerability to be exploitable.
-
Confirm lack of authentication requirementAttempt to access the application's API or web endpoints without providing credentials. Observe if the server accepts unauthenticated requests or returns authentication prompts.Affected if The application accepts unauthenticated HTTP requests to the Web Access component without redirecting to a login page - this indicates the vulnerable configuration.
User is affected if Oracle Primavera Portfolio Management is installed with version 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 its Web Access component is accessible via HTTP without requiring authentication.
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 relevant security patch for this CVE. Additionally, restrict network access to the Primavera Portfolio Management web interface to minimize exposure and implement additional CSRF/tampering protections given the human-interaction requirement.
- 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-2022-21269 — 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-21269 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