CVE-2020-2782
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: Query). 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 and unauthorized ability to cause a partial denial of service (partial DOS) of PeopleSoft Enterprise PeopleTools. CVSS 3.0 Base Score 7.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 · high confidenceCVE-2020-2782 is a vulnerability in the PeopleSoft Enterprise PeopleTools Query component affecting versions 8.56, 8.57, and 8.58. The flaw allows an unauthenticated remote attacker with network access via HTTP to manipulate query operations, resulting in unauthorized read, insert, update, and delete access to a subset of PeopleSoft data, plus partial denial of service. Exploitation requires human interaction from a person other than the attacker.
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.56= 8.57= 8.58CVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 PeopleTools versionAccess PeopleSoft Application Designer or check the psversion.txt file in the PS_HOME directory. Run 'psadmin -about' from the PeopleTools directory to retrieve the installed version number.Affected if The version displayed is 8.56, 8.57, or 8.58 exactly as listed in the affected versions.
-
Verify Query component is enabledCheck if the Query web component is accessible. Navigate to the PeopleSoft web server URL and look for the Query access point, typically under /psp/.../QUERY/ or confirm Query Manager is available in the PIA web interface.Affected if The Query interface is accessible and functional in the PeopleSoft Internet Architecture.
-
Check HTTP/HTTPS network exposureReview the web server configuration (Oracle WebLogic, IBM Http Server) bindings and determine if the PeopleSoft servers are listening on public or untrusted network interfaces. Check firewall rules for inbound access to PeopleSoft HTTP ports (typically 80, 443, or custom ports).Affected if The PeopleSoft Query interface is reachable from networks outside the trusted internal network.
-
Review access logs for Query operationsExamine PeopleSoft application server and web server logs (such as APPSRV.log, HTTP logs) for query operations. Look for query execution patterns, especially from unusual source IP addresses or during unusual hours.Affected if There are query operations matching patterns that were not initiated by legitimate users.
Your environment is likely affected if you have PeopleTools version 8.56, 8.57, or 8.58 with the Query interface exposed to untrusted networks via HTTP/HTTPS.
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 the Oracle critical patch update for CVE-2020-2782 and restrict HTTP/HTTPS access to PeopleSoft Query interfaces to trusted networks only. Monitor for anomalous query patterns indicative of exploitation.
- 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-2020-2782 — 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-2020-2782 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