dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2020-2776

HIGH · 8.6 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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: Security). Supported versions that are affected are 8.56 and 8.57. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. While the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of PeopleSoft Enterprise PeopleTools. CVSS 3.0 Base Score 8.6 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H).

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

A denial of service vulnerability in the Security component of PeopleSoft Enterprise PeopleTools versions 8.56 and 8.57 allows unauthenticated remote attackers via HTTP to crash or hang the application, potentially impacting additional products in the PeopleSoft suite.

MitigationApply the Oracle security patch for CVE-2020-2776; as an interim measure, consider implementing WAF rules or rate limiting on PeopleSoft HTTP endpoints to reduce exploitability.

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

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
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

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 Configuration Manager or check the PS_HOME/pt8.properties file for the Tools Release version. Alternatively, navigate to PeopleSoft Internet Architecture (PIA) and check About > Version in the system information page.
    Affected if The installed version is exactly 8.56 or 8.57.
  2. Confirm HTTP listeners are active
    Check if the PeopleSoft PIA web servers (Weblogic/Websphere) are running and listening on HTTP/HTTPS ports (typically ports 80, 443, 8000, 8080). Use netstat or check the web server administration console.
    Affected if HTTP listeners are exposed and reachable from the network.
  3. Verify PeopleSoft Security component is in use
    Check that the Security component is enabled in the PeopleSoft application. This can be confirmed by accessing the Security > User provisioning pages in PeopleSoft Application Designer or verifying the security tables are populated.
    Affected if The Security component is active and functional in the PeopleSoft environment.
  4. Review HTTP endpoint exposure
    Identify which PeopleSoft HTTP servlets and services are exposed externally. Check the web profile configuration and web server XML files (weblogic.xml, web.xml) for exposed servlet mappings.
    Affected if Unauthenticated HTTP endpoints are accessible without VPN or network segmentation.

A system is affected if it runs PeopleTools version 8.56 or 8.57 with HTTP-accessible endpoints and the Security component is enabled, allowing unauthenticated attackers to crash or hang the application via HTTP requests.

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 security patch for CVE-2020-2776; as an interim measure, consider implementing WAF rules or rate limiting on PeopleSoft HTTP endpoints to reduce exploitability.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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