CVE-2020-2912
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 CS Campus Community product of Oracle PeopleSoft (component: Self-Service). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise CS Campus Community. While the vulnerability is in PeopleSoft Enterprise CS Campus Community, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of PeopleSoft Enterprise CS Campus Community accessible data. CVSS 3.0 Base Score 5.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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 confidenceThis is an information disclosure vulnerability in PeopleSoft Enterprise CS Campus Community Self-Service component (v9.2). The flaw allows low-privileged users with network access via HTTP to gain unauthorized read access to a subset of accessible data. The CVSS vector indicates a changed scope, meaning attacks may impact additional products beyond the immediate target.
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= 9.2CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 PeopleSoft Enterprise CS Campus Community versionAccess PeopleSoft Application Designer or check the system version information through the PeopleSoft Enterprise Portal. Navigate to PeopleTools > About > About PeopleSoft for version details. Alternatively, query the PSVERSION table or check the installation manifest files for the Campus Community (CS) module version.Affected if The installed version is exactly 9.2 (version equals 9.2)
-
Verify Campus Community Self-Service component is enabledLog into PeopleSoft Enterprise Portal as an administrator. Navigate to PeopleTools > Portal > Structure and Content. Expand the Content References and check if Self-Service modules under Campus Community are present and set to Active status.Affected if The Self-Service component is installed and enabled in the portal structure
-
Confirm HTTP/HTTPS network accessibility to the PeopleSoft web serverCheck the web profile configuration in PeopleSoft (PeopleTools > Web Profile > Web Profile Configuration). Verify that the web server is reachable over HTTP (port 80/443) and note whether authentication is required for Self-Service pages.Affected if The Self-Service interface is accessible over HTTP without requiring elevated privileges
-
Review Self-Service user role permissionsAccess PeopleSoft Security through PeopleTools > Security > User Profiles or Role Permissions. Examine roles assigned to low-privileged users who have access to the Campus Community Self-Service module. Check for excessive data access permissions.Affected if Low-privileged (non-admin) users have access to Self-Service and can potentially view data outside their authorized scope
A user is affected if they run PeopleSoft Enterprise CS Campus Community version 9.2 with the Self-Service component enabled and accessible over the network to low-privileged users.
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 PeopleSoft Critical Patch Update (CPU) containing the fix for CVE-2020-2912. Review and restrict user permissions in the Self-Service module to enforce least-privilege access controls.
- 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-2912 — 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-2912 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