CVE-2024-21065
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 PeopleTools product of Oracle PeopleSoft (component: Workflow). 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 confidenceA vulnerability in the PeopleSoft Enterprise PeopleTools Workflow component allows unauthenticated attackers with network access via HTTP to perform unauthorized read, insert, update, and delete operations on accessible data. The flaw is easily exploitable but requires human interaction (such as clicking a malicious link) to trigger, and due to scope change, may impact additional products beyond PeopleSoft.
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= 8.59= 8.60= 8.61CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleSoft PeopleTools installation and versionLocate the PeopleSoft installation directory and check the version.properties or version.txt file, or use the PeopleSoft Configuration Manager to view the installed PeopleTools version. Alternatively, query the PSSTATUS table in the PeopleSoft database or check the PeopleSoft Home directory for version information.Affected if The installed PeopleTools version is 8.59.x, 8.60.x, or 8.61.x (any minor release within these major versions)
-
Confirm the Workflow component is enabledAccess the PeopleSoft Application Designer or PeopleSoft Pure Internet Architecture and navigate to the Workflow component settings. Check if the Workflow engine is enabled in the PeopleTools > Workflow > Workflow Settings. For command-line verification, check the PSSTATUS table or configuration files for WORKFLOW_ENABLED flag.Affected if The Workflow component is enabled and configured in the PeopleSoft environment
-
Verify HTTP-based Workflow exposureCheck if the PeopleSoft Pure Internet Architecture (PIA) web servers are running and accessible via HTTP/HTTPS. Review the web server configuration (weblogic.xml, web.xml) to confirm Workflow-related servlets and handlers are exposed. Use a browser or curl to access common Workflow URLs such as /psc/ps/EMPLOYEE/HRMS/c/ROLE_MANAGER. and check for response.Affected if The PeopleSoft web interfaces are accessible over HTTP/HTTPS and the Workflow servlet is exposed without additional authentication barriers
-
Review Workflow routing and notification configurationsUse PeopleSoft Application Designer or query the PSROUTINGDEFN, PSNOTIFYMSG, and related Workflow routing tables to review configured routings. Check for any suspicious or unauthorized routing entries that may indicate exploitation. Look for routings to external addresses or unexpected trigger conditions.Affected if Unauthorized or unexpected workflow routing definitions exist in the system or notification messages have been sent to unknown recipients
You are affected if your environment runs PeopleSoft Enterprise PeopleTools versions 8.59, 8.60, or 8.61 with the Workflow component enabled and accessible via HTTP, particularly if users could be tricked into clicking malicious links.
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.
dbcve · scopedApply the relevant Oracle PeopleSoft Enterprise PeopleTools patch for versions 8.59, 8.60, and 8.61 as soon as possible. Until patches are applied, restrict network access to PeopleSoft interfaces and educate users about clicking untrusted links.
Upgrade to the latest PeopleTools version (8.62 or later) that includes the CVE-2024-21065 fix from Oracle's Critical Patch Update
- Confirm current PeopleTools version by navigating to PeopleTools > About in the PeopleSoft application
- Review Oracle's Critical Patch Update documentation for CVE-2024-21065 to obtain the specific patch or fixed version
- Apply the recommended patch or upgrade to the next stable PeopleTools release that includes the fix
- After applying the fix, test the Workflow component to verify the open redirect vulnerability is resolved
- Verify that existing Workflow configurations and integrations function correctly post-fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21065 — 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-21065 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