CVE-2022-21359
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: Optimization Framework). Supported versions that are affected are 8.57, 8.58 and 8.59. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools 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 confidenceThis is an access control vulnerability in the Oracle PeopleSoft Enterprise PeopleTools Optimization Framework component. It allows unauthenticated remote attackers to perform unauthorized read, insert, update, and delete operations on a subset of accessible data through the HTTP interface. The attack requires human interaction and can impact additional products beyond the core PeopleTools.
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.57= 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
- 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.
-
Identify installed PeopleTools versionLocate the PeopleTools version by checking the PS_HOME directory properties file (psappsrv.properties or psprcs.cfg) or by querying the PSVERSION table in the database. On the application server, run 'psadmin -about' or check the About page in PeopleSoft Pure Internet Architecture.Affected if The installed version is exactly 8.57, 8.58, or 8.59
-
Verify HTTP/HTTPS exposure of PeopleSoftCheck if the PeopleSoft Pure Internet Architecture (PIA) web servers (WebLogic/Oracle HTTP Server) are listening on ports 80, 443, or custom ports. Confirm which URLs are accessible externally versus internally using network scans or web server configuration review.Affected if The PeopleSoft HTTP interface is exposed to untrusted networks or the internet
-
Confirm Optimization Framework is enabledReview PeopleSoft configuration files (psappsrv.cfg, psprcs.cfg) and the PeopleSoft Application Designer to determine if the Optimization Framework components and related services are installed and active.Affected if The Optimization Framework component is installed and running on the affected PeopleTools version
-
Review access control configurationExamine the web profile settings (Web Profile Configuration in PeopleSoft), IIS/WebLogic security configurations, and any URL access restrictions. Check if anonymous access is permitted to the PSOPRDEFNDIR or optimization-related servlets.Affected if Anonymous or unauthenticated HTTP access to optimization-related endpoints is permitted
You are affected if your PeopleSoft Enterprise PeopleTools is version 8.57, 8.58, or 8.59 AND the HTTP interface is exposed with the Optimization Framework enabled and no additional access controls on the vulnerable endpoints.
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 the relevant Oracle Critical Patch Update (CPU) for January 2022 or later that addresses CVE-2022-21359. If patches are unavailable, consider restricting network access to PeopleSoft HTTP endpoints and implementing additional application-layer access controls.
Oracle PeopleSoft Enterprise PeopleTools 8.60 or later (or apply Jan 2022 CPU patches to your current version)
- Review the January 2022 Oracle Critical Patch Update (CPU) for CVE-2022-21359 at https://www.oracle.com/security-alerts/cpujan2022.html
- Identify the specific PeopleTools patch bundle from the CPU applicable to your version (8.57, 8.58, or 8.59)
- Download the patch from Oracle Support (My Oracle Support) using the patch numbers listed in the CPU advisory
- Apply the patch in a non-production environment first to validate compatibility
- Schedule a maintenance window and apply the patch to production systems
- Verify the patch was applied successfully by checking the PeopleTools version and testing the Optimization Framework functionality
Generated from the published advisory — verify against the referenced sources before acting.
- 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-21359 — 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-21359 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