CVE-2024-21063
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 HCM Benefits Administration product of Oracle PeopleSoft (component: Benefits Administration). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where PeopleSoft Enterprise HCM Benefits Administration executes to compromise PeopleSoft Enterprise HCM Benefits Administration. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise HCM Benefits Administration accessible data as well as unauthorized update, insert or delete access to some of PeopleSoft Enterprise HCM Benefits Administration accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of PeopleSoft Enterprise HCM Benefits Administration. CVSS 3.1 Base Score 6.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L).
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 · moderate confidenceVulnerability in PeopleSoft Enterprise HCM Benefits Administration (version 9.2) allows a low-privileged attacker with local infrastructure logon access to compromise the system through human interaction from another user. The flaw enables unauthorized access to critical data, unauthorized update/insert/delete operations, and partial denial of service.
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= 9.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L
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 if PeopleSoft Enterprise HCM is installedLocate PeopleSoft installation directories and check for HCM (Human Capital Management) components. Common paths include the PS_HOME directory and associated application files.Affected if PeopleSoft Enterprise HCM Benefits Administration is present on the system
-
Determine the installed version of Benefits AdministrationUse PeopleSoft administrative tools (Application Designer, version info utilities, or PS.VERSION records) to query the exact version number of the Benefits Administration module.Affected if The version is exactly 9.2 (as indicated by = 9.2 in affected products)
-
Verify if Benefits Administration module is configured or activeCheck PeopleSoft database tables or configuration settings related to Benefits Administration (such as PS_BN_* tables or module activation status). Consult PeopleSoft system tables for active HCM components.Affected if Benefits Administration module is configured, enabled, or actively used in the environment
-
Assess local infrastructure access controlsReview user access permissions and determine whether low-privileged accounts have local infrastructure logon capability to the PeopleSoft application servers or database hosts.Affected if Low-privileged users have local infrastructure logon access to PeopleSoft servers or related infrastructure
-
Evaluate exposure to human interaction attack vectorDetermine if the environment permits scenarios where one user could interact with another user's session or trigger social engineering scenarios through the Benefits Administration interface.Affected if Users can be targeted through human interaction within the Benefits Administration workflow
You are affected if PeopleSoft Enterprise HCM Benefits Administration version 9.2 is installed AND low-privileged users have local infrastructure logon access AND the module is configured for use, creating the conditions for human interaction-based exploitation.
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.
From vendor dataApply Oracle's published patch for CVE-2024-21063 when available; in the interim, restrict local access to the PeopleSoft infrastructure and minimize user exposure to social engineering vectors requiring human interaction.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21063 — 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-2024-21063 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