dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2020-14832

MEDIUM · 6.1 CVSS v3.1 Published 2020-10-21
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: Integration Broker). Supported versions that are affected are 8.56, 8.57 and 8.58. 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. 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 remote attacker can exploit a flaw in the PeopleSoft Integration Broker component via HTTP to achieve unauthorized read and modify access to some PeopleSoft data. The attack requires human interaction (UI:R) and can impact additional products due to scope change (S:C).

MitigationApply the Oracle Critical Patch Update for PeopleSoft Enterprise PeopleTools for the affected versions (8.56, 8.57, 8.58). Consider restricting network exposure of Integration Broker endpoints and implementing WAF rules as an interim control.

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.56= 8.57= 8.58

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. Identify installed PeopleTools version
    Log into PeopleSoft Application Designer or navigate to PeopleTools > About PeopleTools to view the version number. Alternatively, query the PSVERSION table or check the About page in the web application.
    Affected if The version is 8.56, 8.57, or 8.58 exactly.
  2. Verify Integration Broker is enabled
    Navigate to PeopleTools > Integration Broker > Integration Setup > Service Configuration or check the IB domain status via WebLogic/Node Manager console.
    Affected if Integration Broker is running and the IB domain is active.
  3. Confirm Integration Broker HTTP listeners are exposed
    Check the Integration Gateway URL configuration (typically /PSIGW/HttpListeningConnector) and verify external network accessibility. Review web server configuration for exposed Integration Broker endpoints.
    Affected if HTTP listeners for Integration Broker are accessible from untrusted networks without authentication barriers.
  4. Review Integration Broker security configuration
    Navigate to PeopleTools > Integration Broker > Configuration > Security and verify whether anonymous access or weak authentication is permitted on the listening connectors.
    Affected if Anonymous or unauthenticated HTTP access is allowed on Integration Broker connectors.

You are affected if your PeopleTools version is exactly 8.56, 8.57, or 8.58 AND Integration Broker HTTP endpoints are accessible and permit unauthenticated access.

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 the Oracle Critical Patch Update for PeopleSoft Enterprise PeopleTools for the affected versions (8.56, 8.57, 8.58). Consider restricting network exposure of Integration Broker endpoints and implementing WAF rules as an interim control.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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