CVE-2022-21376
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 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 confidenceUnauthenticated HTTP vulnerability in Oracle Primavera Portfolio Management's Web Access component allows remote attackers to perform unauthorized read and limited write operations on a subset of data without credentials. Exploitation requires victim interaction (social engineering/luring to click malicious link), and attacks impact confidentiality and integrity but 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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Oracle Primavera Portfolio ManagementLocate the product version through the application itself, administrative console, or installation directory metadata. Common paths include the application administration pages or the installation manifest file.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 equals exactly 20.0.0.0
-
Confirm the Web Access component is enabled and accessibleVerify the Web Access component is currently running and reachable via HTTP/HTTPS. This is typically the web interface used for browser-based access to the application.Affected if The Web Access component is enabled and exposed over the network, making it reachable to potential attackers
-
Determine if the Web Access interface is exposed to untrusted networksReview network configuration, firewall rules, or reverse proxy settings to determine whether the Web Access URL is accessible from outside the trusted internal network or the internet.Affected if The Web Access interface is reachable from untrusted networks or the public internet without proper network segmentation or authentication barriers in place
-
Inspect HTTP access logs for signs of unauthenticated access attemptsReview web server or application logs for HTTP requests that accessed data endpoints without corresponding successful authentication events, or for anomalous data access patterns.Affected if Logs show data access or read/write operations from IP addresses that did not authenticate or that occurred outside normal authenticated sessions
You are affected if the installed version is any of the affected versions listed AND the Web Access component is enabled and network-accessible to potential 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.
dbcve · scopedApply Oracle Critical Patch Update (CPU) containing the security fix for this vulnerability. If immediate patching is not feasible, restrict network exposure of the Web Access interface and implement web application firewall rules to detect malicious HTTP requests.
Upgrade to 18.0.3.1+, 19.0.1.3+, or 20.0.0.1+ (or latest stable release beyond affected versions)
- 1. Identify the currently installed Primavera Portfolio Management version from the affected list (18.0.0.0-18.0.3.0, 19.0.0.0-19.0.1.2, or 20.0.0.0)
- 2. Download the patched version from Oracle Support (My Oracle Support) - search for patch relevant to CVE-2022-21376
- 3. Apply the patch following Oracle's standard patch application procedure for Primavera Portfolio Management
- 4. Alternatively, upgrade to a version beyond the affected ranges (e.g., 18.0.3.1 or higher, 19.0.1.3 or higher, or 20.0.0.1 or higher)
- 5. After applying patch or upgrade, verify the Web Access component is functioning correctly
- 6. Test that the vulnerability is remediated by verifying unauthorized read/write operations are blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21376 — 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-21376 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