dbcve.org
Peoplesoft Enterprise Cs Sa Integration PackApplication · Oracle

CVE-2022-21300

HIGH · 7.5 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 CS SA Integration Pack product of Oracle PeopleSoft (component: Snapshot Integration). Supported versions that are affected are 9.0 and 9.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise CS SA Integration Pack. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise CS SA Integration Pack accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 confidence

Unauthenticated HTTP vulnerability in the Snapshot Integration component of PeopleSoft Enterprise CS SA Integration Pack (versions 9.0 and 9.2) allows remote attackers to access sensitive data without credentials. The flaw has high confidentiality impact with no integrity or availability effects, and is exploitable over the network with low complexity and no user interaction required.

MitigationApply Oracle's latest Critical Patch Update for PeopleSoft to address this vulnerability. As an interim control, restrict HTTP access to the affected Snapshot Integration endpoint via network segmentation or a Web Application Firewall.

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 Cs Sa Integration PackApplication
Affected:= 9.0= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify PeopleSoft Enterprise CS version
    Access PeopleSoft Configuration Manager or check the About page in the PeopleSoft application to determine the exact installed version of PeopleSoft Enterprise CS
    Affected if Version displayed is exactly 9.0 or exactly 9.2 (matching the affected versions)
  2. Verify SA Integration Pack is installed
    Check the PeopleSoft Component Registry or the installed Integration Packs list within the PeopleSoft Application Designer or PeopleSoft Administrator to confirm the SA Integration Pack is present
    Affected if SA Integration Pack is found installed on the system
  3. Confirm Snapshot Integration component is configured
    Navigate to the Snapshot Integration component in PeopleSoft Enterprise Manager or check the Integration Broker registry to see if the Snapshot Integration service is enabled
    Affected if Snapshot Integration component is enabled or configured in the environment
  4. Check HTTP endpoint exposure
    Identify the HTTP listener ports configured for the PeopleSoft web server (usually via WebLogic or WebSphere console) and determine if port 80/443 or the PeopleSoft HTTP service is accessible from untrusted networks
    Affected if The PeopleSoft HTTP port is exposed to the internet or untrusted internal networks without network segmentation
  5. Test unauthenticated access to Snapshot Integration
    Using a web browser or HTTP client, attempt to access the Snapshot Integration endpoint path (typically under /PSIGW/PeopleSoftServiceListeningConnector or similar Integration Broker paths) without providing credentials
    Affected if The endpoint returns sensitive data or valid responses without requiring authentication

A system is affected if it runs PeopleSoft Enterprise CS version 9.0 or 9.2 with the SA Integration Pack installed, has the Snapshot Integration component enabled, and the HTTP endpoint is network-accessible without proper authentication controls.

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 Oracle's latest Critical Patch Update for PeopleSoft to address this vulnerability. As an interim control, restrict HTTP access to the affected Snapshot Integration endpoint via network segmentation or a Web Application Firewall.

Fix this in Peoplesoft Enterprise Cs Sa Integration Pack Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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