dbcve.org
Peoplesoft EnterpriseApplication · Oracle

CVE-2022-21481

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 FIN Cash Management product of Oracle PeopleSoft (component: Financial Gateway). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise FIN Cash Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise FIN Cash Management, 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 FIN Cash Management accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise FIN Cash Management accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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

This is an unauthenticated vulnerability in PeopleSoft Enterprise FIN Cash Management's Financial Gateway component (version 9.2). A low-privileged attacker with network access via HTTP can achieve unauthorized read and write (insert/update/delete) access to a subset of the application's data. Successful exploitation requires human interaction from a person other than the attacker.

MitigationApply the Oracle PeopleSoft bundle/patch that addresses CVE-2022-21481, typically available through Oracle's quarterly Critical Patch Updates. Given the data access impact, verify Financial Gateway functionality post-patch.

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 EnterpriseApplication
Affected:= 9.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm PeopleSoft Enterprise version 9.2 is installed
    Access PeopleSoft Application Designer or use the version check utility (PSADMIN about or the System Diagnostics page) to identify the exact PeopleTools/Application version. Check if the deployed application version matches 9.2.
    Affected if The installed PeopleSoft Enterprise version is exactly 9.2 (or includes 9.2 in a mixed-mode deployment).
  2. Verify Financial Gateway component is enabled
    Log into PeopleSoft Enterprise Navigator and check if the Financial Gateway module (under Enterprise Components > Financial Gateway) is present and active in the application menu structure. Alternatively, query the PSCLASSDEFN table or check component registry entries for component ID 'FS_FIN_GW' or similar Financial Gateway components.
    Affected if Financial Gateway is listed as an available component and is accessible to users in the application.
  3. Check Financial Gateway data access configuration
    Navigate to Financial Gateway setup pages (Set Up Financial Gateway > Installation) and review the data source configurations. Identify if external or internal data sources are configured that could be exposed.
    Affected if One or more Financial Gateway data sources are configured and accessible through the application.
  4. Assess network exposure of PeopleSoft web services
    Review web tier configuration (WebLogic/PeopleSoftPIA web server) to determine if HTTP/HTTPS endpoints for Financial Gateway are exposed externally or to untrusted networks. Check the PeopleSoft Pure Internet Architecture URL patterns.
    Affected if The PeopleSoft HTTP endpoints are reachable from untrusted networks without proper network segmentation or VPN.
  5. Review user access controls for Financial Gateway
    Use PeopleSoft Permission Lists and Role management (PeopleTools > Security > Permissions & Roles) to identify which low-privileged users have access to Financial Gateway components. Check if guest or minimal-privilege roles can access the gateway functions.
    Affected if Users with minimal privileges (such as guest users or those with only basic financial roles) can access Financial Gateway components.

You are affected if running PeopleSoft Enterprise 9.2 with Financial Gateway enabled and exposed to network access, regardless of user privilege level, since exploitation can achieve unauthorized data access through the vulnerable component.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle PeopleSoft bundle/patch that addresses CVE-2022-21481, typically available through Oracle's quarterly Critical Patch Updates. Given the data access impact, verify Financial Gateway functionality post-patch.

Fix this in Peoplesoft Enterprise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21481 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-21481 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