dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2024-21178

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-16
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: Portal). Supported versions that are affected are 8.59, 8.60 and 8.61. 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 vulnerability in the PeopleSoft Enterprise PeopleTools Portal component (versions 8.59, 8.60, 8.61) allows remote attackers via HTTP to achieve unauthorized read and write access to a subset of accessible data. The attack requires human interaction (likely social engineering to trick a user) and may impact additional products beyond PeopleSoft due to scope change.

MitigationApply the Oracle security patch for CVE-2024-21178 to all affected PeopleSoft Enterprise PeopleTools installations. Additionally, restrict network access to the Portal interface and implement user awareness training given the required human interaction vector.

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.59= 8.60= 8.61

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. Confirm PeopleSoft PeopleTools installation
    Locate the PeopleTools installation directory and check for the PTVERSION file or use Oracle's SQL query: SELECT VERSION FROM PSVERSION WHERE OBJECTTYPE = 'ToolsRelease';
    Affected if PeopleSoft Enterprise PeopleTools is not installed - you are not affected
  2. Identify installed PeopleTools version
    Run Oracle SQL query: SELECT VERSION FROM PSVERSION WHERE OBJECTTYPE = 'ToolsRelease'; or check the psjoa.jar file version in the PeopleSoft web profile directory
    Affected if The installed version is exactly 8.59, 8.60, or 8.61 - you are affected
  3. Verify Portal component is enabled
    Check the PeopleSoft Portal configuration via the web profile settings in PeopleSoft Application Designer or by querying the PSAPPSRV cache configuration for Portal-related modules
    Affected if Portal (PTAUTHENTICATION or Portal servlet) is enabled and accessible - you are affected
  4. Check HTTP network exposure
    Review web server configuration (Oracle WebLogic, IBM WebSphere, or IIS) to determine if the PeopleSoft Portal interface is exposed over HTTP/HTTPS to untrusted networks
    Affected if Portal is accessible via HTTP from untrusted networks - you are affected and at higher risk

You are affected if PeopleSoft Enterprise PeopleTools versions 8.59, 8.60, or 8.61 are installed with the Portal component enabled and accessible via HTTP.

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 the Oracle security patch for CVE-2024-21178 to all affected PeopleSoft Enterprise PeopleTools installations. Additionally, restrict network access to the Portal interface and implement user awareness training given the required human interaction vector.

Recommended fix Moderate confidence

Oracle PeopleSoft Enterprise PeopleTools 8.62 or later (or apply Oracle CPU patch for versions 8.59/8.60/8.61)

  1. 1. Identify the current PeopleSoft Enterprise PeopleTools version in use (8.59, 8.60, or 8.62+).
  2. 2. Navigate to Oracle Support (support.oracle.com) and search for CVE-2024-21178 or the related Critical Patch Update.
  3. 3. Download and apply the Oracle Critical Patch Update (CPU) that addresses this vulnerability for PeopleSoft Enterprise PeopleTools.
  4. 4. For PeopleTools 8.59, apply the latest patch set update (PSU) for that version line.
  5. 5. For PeopleTools 8.60, apply the latest patch set update (PSU) for that version line.
  6. 6. For PeopleTools 8.61, apply the latest patch set update (PSU) for that version line.
  7. 7. After applying patches, clear the PeopleSoft web server caches and restart the PeopleSoft application server and web server domains.
  8. 8. Verify the patch was applied successfully by checking the version and testing the Portal component for XSS vulnerability resolution.
Caveat Patches should be tested in non-production environment first; some customizations may need adjustment after PSU application

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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