CVE-2022-21470
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: Process Scheduler). Supported versions that are affected are 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 (scope change). 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 confidenceUnauthenticated network attack against PeopleSoft Enterprise PeopleTools Process Scheduler component allows an attacker without credentials to read a subset of data and perform unauthorized updates/inserts/deletes. Exploitation requires user interaction (UI:R), and while scope changes (S:C) may impact additional products, the impact is limited to low confidentiality and integrity 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
- 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 versionQuery the PeopleSoft system for the current PeopleTools version using SQL against the PSVERSION table or via the PeopleSoft Enterprise Portal About pageAffected if The installed version is exactly 8.58 or exactly 8.59
-
Confirm Process Scheduler component is enabledVerify the Process Scheduler (PSAESRV) service is configured and active in the PeopleSoft environment through the Process Scheduler configuration settingsAffected if Process Scheduler component is enabled and accessible
-
Assess network exposure of Process SchedulerDetermine if the Process Scheduler web interface or RPC endpoints are reachable from untrusted networks by reviewing network firewall rules and load balancer configurationsAffected if Process Scheduler interfaces are exposed to unauthenticated network access without proper network segmentation
-
Evaluate user interaction riskReview whether users with access to Process Scheduler could be socially engineered to trigger malicious requests, as exploitation requires user interactionAffected if Users can be tricked into initiating requests that enable the attack
A user is affected if their environment runs PeopleTools version 8.58 or 8.59 with the Process Scheduler component enabled and exposed to network access where an attacker could leverage user interaction to read or modify data.
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 Oracle PeopleSoft Enterprise PeopleTools patch for versions 8.58 and 8.59. As an interim control, restrict network access to Process Scheduler interfaces and educate users about social engineering vectors used to trigger the required interaction.
Upgrade to the latest available PeopleTools 8.58.x or 8.59.x patch level (or migrate to a newer supported version such as 8.60+)
- 1. Identify the current PeopleTools version by navigating to PeopleSoft Enterprise Home > About PeopleTools > About
- 2. Download the latest Critical Patch Update (CPU) for PeopleSoft from Oracle's support website (support.oracle.com)
- 3. Apply the Oracle PeopleTools patch that addresses CVE-2022-21470 - this will be included in the quarterly security patch set
- 4. After patching, verify the version has been updated and confirm the Process Scheduler component is patched
- 5. Test the Process Scheduler functionality to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation12.0 h
- Testing8.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21470 — 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-21470 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