Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2022-21456

MEDIUM · 6.1 CVSS v3.1 Published 2022-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Navigation Pages, Portal, Query). 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 confidence

An unauthenticated network attacker can exploit a vulnerability in PeopleSoft Enterprise PeopleTools Navigation Pages, Portal, or Query components via HTTP. The flaw allows limited unauthorized read and write (insert/update/delete) access to data without credentials, but requires human interaction (such as clicking a malicious link) to trigger. The scope extends beyond PeopleSoft to impact additional products.

MitigationApply Oracle Critical Patch Update April 2022 for PeopleSoft Enterprise PeopleTools 8.58 and 8.59. Restrict network exposure of PeopleSoft interfaces and implement WAF rules as compensating controls until patching is feasible.

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
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.58= 8.59

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if PeopleSoft Enterprise PeopleTools is deployed
    Locate PeopleSoft installation directories or running services. Check for processes named psapsrv, pshpapache, or web profiles serving PeopleSoft applications.
    Affected if PeopleSoft Enterprise PeopleTools software is present in the environment
  2. Determine installed PeopleTools version
    Access the PeopleSoft About page (typically via 'About This Page' in the PeopleSoft banner) or query the PSVERSION table in the database. Compare the version to 8.58 or 8.59.
    Affected if Installed version matches 8.58 or 8.59 exactly
  3. Verify HTTP accessibility of affected components
    Confirm that Navigation Pages, Portal, or Query components are accessible via HTTP/HTTPS. Test access to common paths like /psp, /psc, /psq, or portal URLs. Check if these endpoints respond without authentication.
    Affected if Navigation Pages, Portal, or Query components are reachable via HTTP without authentication
  4. Assess network exposure of PeopleSoft interfaces
    Determine if PeopleSoft web servers are reachable from untrusted networks. Review firewall rules, load balancer configurations, and reverse proxy settings that expose PeopleSoft ports (typically 80, 443, or custom ports) to the internet or less-trusted network segments.
    Affected if PeopleSoft HTTP interfaces are exposed to untrusted networks or the internet

Environment is affected if running PeopleSoft Enterprise PeopleTools version 8.58 or 8.59 with Navigation Pages, Portal, or Query components accessible via HTTP to unauthenticated network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update April 2022 for PeopleSoft Enterprise PeopleTools 8.58 and 8.59. Restrict network exposure of PeopleSoft interfaces and implement WAF rules as compensating controls until patching is feasible.

Recommended fix High confidence

PeopleSoft Enterprise PeopleTools 8.60 or later

  1. Download PeopleSoft Enterprise PeopleTools 8.60 or later from Oracle's official support portal (My Oracle Support)
  2. Review Oracle's PeopleTools upgrade documentation for your specific product version
  3. Ensure you have a complete backup of your production database and file system before proceeding
  4. Test the upgrade in a non-production environment first to verify compatibility with your customizations
  5. Schedule a maintenance window as the upgrade will require system downtime
  6. Apply the upgrade following Oracle's standard PeopleTools upgrade procedures
  7. After upgrade, verify that the Navigation Pages, Portal, and Query components are functioning correctly
  8. Confirm the vulnerability is resolved by reviewing the Oracle Critical Patch Update documentation for the version you upgraded to
Caveat Review Oracle's PeopleTools 8.60 migration guide for potential compatibility impacts with customizations and integrations; thorough testing in a non-production environment is strongly recommended before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21456 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21456 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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