CVE-2022-21364
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: Weblogic). Supported versions that are affected are 8.57, 8.58 and 8.59. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 confidenceInformation disclosure vulnerability in the Weblogic component of PeopleSoft Enterprise PeopleTools versions 8.57, 8.58, and 8.59. Allows unauthenticated attackers with network access via HTTP to read a subset of accessible data due to improper access controls in the Weblogic integration.
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.57= 8.58= 8.59CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed PeopleTools versionLocate the PeopleTools installation directory and check the version file or use the PSADMIN utility to query the installed version. Common locations include the PS_HOME directory or check the version.properties file typically found in the PeopleTools installation path.Affected if The installed version matches exactly 8.57, 8.58, or 8.59 (the affected versions). Versions before 8.57 or beyond 8.59 are not affected by this specific CVE.
-
Verify Weblogic component is presentConfirm that the Weblogic Server component is installed as part of the PeopleSoft deployment. Check for Weblogic domain configurations under the PeopleTools installation, typically in a domains directory or via the Weblogic Administration Console.Affected if Weblogic is installed and configured as part of the PeopleSoft environment. If Weblogic is not used (e.g., only Tuxedo/application server), the vulnerability may not apply.
-
Check Weblogic HTTP listener configurationExamine the Weblogic configuration files (config.xml) or access the Weblogic Administration Console to determine if HTTP listeners are enabled on the affected ports (default 80/443 or configured ports). Look for Network Access Points configured for HTTP protocol.Affected if HTTP listeners are enabled and accessible on Weblogic ports. The vulnerability specifically requires HTTP network access to exploit.
-
Assess network exposure of Weblogic interfacesReview network configuration, firewall rules, and load balancer settings to determine if Weblogic HTTP ports are exposed to untrusted networks. Use netstat or port scanning tools to identify listening HTTP services on the PeopleSoft host.Affected if Weblogic HTTP interfaces are reachable from untrusted/network-accessible locations. The CVE requires network access via HTTP from unauthenticated attackers.
A user is affected if they have PeopleTools version 8.57, 8.58, or 8.59 with Weblogic HTTP interfaces exposed to network access, as the vulnerability requires both the vulnerable version and HTTP accessibility to be exploited.
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 Oracle Critical Patch Update (CPU) containing the fix for CVE-2022-21364, or upgrade to a patched PeopleSoft Enterprise PeopleTools version beyond 8.59. Restrict HTTP/HTTPS exposure to Weblogic interfaces via network segmentation as an interim control.
PeopleSoft Enterprise PeopleTools 8.60 or later (with January 2022 CPU applied)
- Upgrade PeopleSoft Enterprise PeopleTools to a version beyond 8.59 where the vulnerability is patched
- Apply the January 2022 Critical Patch Update (CPU) from Oracle which includes the fix for CVE-2022-21364
- After upgrading, verify the Weblogic component is updated and confirm the vulnerability is remediated through testing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21364 — 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-2022-21364 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