CVE-2021-2421
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: Integration and Interfaces). Supported versions that are affected are 9.0 and 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise CS Campus Community. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise CS Campus Community accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 confidenceImproper authorization vulnerability in the Integration and Interfaces component of PeopleSoft Enterprise CS Campus Community allows low-privileged attackers with network access via HTTP to access critical data. The vulnerability stems from missing or inadequate access controls on integration endpoints, enabling unauthorized data exposure.
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.0= 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Campus Community versionAccess the PeopleSoft Enterprise Campus Community system and locate the version information, typically found in the Pure Internet Architecture login page footer, system about page, or via the PSADMIN utility version checkAffected if The installed version matches 9.0 or 9.2 (including any subversions within these releases)
-
Verify Integration and Interfaces component is configuredCheck if the Integration Broker or Integration Gateway components are enabled in the PeopleSoft environment, typically through the PeopleSoft Application Designer or Integration Broker configuration pagesAffected if Integration Broker or related integration services are active and exposed
-
Inspect integration endpoint accessibilityTest network access to common PeopleSoft integration endpoints (such as /PSIGW/PeopleSoftServiceListeningConnector) using a low-privileged or unauthenticated HTTP request to determine if endpoints respond without authorizationAffected if Integration endpoints respond to unauthenticated or low-privileged network requests
-
Review access control configuration on integration interfacesExamine the role-based access control (RBAC) settings for integration interfaces through the PeopleSoft Security Administration console, specifically checking permission lists and roles assigned to integration gateway and service operationsAffected if Integration interfaces lack proper role restrictions or allow access from low-privileged or unauthorized roles
A system is affected if it runs PeopleSoft Enterprise CS Campus Community version 9.0 or 9.2 with integration endpoints accessible to low-privileged network users without adequate access controls.
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 Oracle Critical Patch Update (CPU) containing the security fix for this vulnerability. Additionally, review and enforce proper role-based access controls (RBAC) on integration interfaces and consider network segmentation to limit exposure.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2421 — 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-2021-2421 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