CVE-2022-21345
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 PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Security). Supported versions that are affected are 8.58 and 8.59. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 PeopleSoft Enterprise PeopleTools Security component affecting versions 8.58 and 8.59. Allows low-privileged attackers with network access via HTTP to compromise the system and gain unauthorized access to critical data. Confidentiality-focused attack with high impact but no integrity or availability compromise.
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= 8.58= 8.59CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 PeopleSoft PeopleTools installationCheck for PeopleSoft Enterprise PeopleTools installation by looking for PS_HOME environment variable, or search for psadmin.exe or the PeopleTools directory structure on the systemAffected if PeopleSoft Enterprise PeopleTools is not installed, the system is not affected
-
Determine PeopleTools versionAccess PeopleSoft Administration > About PeopleSoft page, or check the version.txt file in the PS_HOME directory, or run the following SQL: SELECT version FROM psstatusAffected if The installed version is exactly 8.58 or exactly 8.59 (these are the only affected versions)
-
Verify HTTP/HTTPS interface is exposedCheck the PeopleSoft Application Server and Process Scheduler configuration (psappsrv.cfg, psprcs.cfg) for HTTP listeners, or verify that the PeopleSoft Pure Internet Architecture (PIA) web server is accessible on network interfacesAffected if HTTP or HTTPS listeners are enabled and accessible over the network (network access is required for exploitation)
-
Confirm external network exposureReview firewall rules and network configuration to determine if PeopleSoft HTTP ports (typically 80, 443, or custom ports) are accessible from untrusted networksAffected if The HTTP interface is reachable from outside the trusted network (this increases exposure but is not strictly required for internal attackers)
-
Review user access controlsExamine PeopleSoft permission lists and role assignments to identify low-privileged accounts that have any PeopleTools or Security component accessAffected if Low-privileged users with any PeopleTools or Security component access exist in the system (these users can exploit the vulnerability)
A system is affected if it runs PeopleTools version 8.58 or 8.59 with HTTP network access enabled and has low-privileged users who can access the system remotely.
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 for PeopleSoft Enterprise PeopleTools addressing this vulnerability. Until patch is applied, restrict network access to PeopleSoft HTTP interfaces and enforce least-privilege user permissions.
PeopleSoft Enterprise PeopleTools 8.60 or later
- Navigate to Oracle Support and download the January 2022 Critical Patch Update (CPU) for PeopleSoft Enterprise PeopleTools
- Apply the security patch for CVE-2022-21345 following Oracle's patch application instructions
- Alternatively, upgrade PeopleSoft Enterprise PeopleTools to version 8.60 or later which contains the security fix
- After applying the patch or upgrade, verify the Security component is functioning correctly
- Test that low-privileged user access controls are properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21345 — 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-21345 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