CVE-2012-3113
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 · uneditedUnspecified vulnerability in the PeopleSoft Enterprise HRMS component in Oracle PeopleSoft Products 9.0.20 allows remote authenticated users to affect confidentiality and integrity, related to EPERF.
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 · moderate confidenceUnspecified vulnerability in Oracle PeopleSoft Enterprise HRMS 9.0.20's EPERF (ePerformance/Employee Performance Review) module allows remote authenticated users to impact confidentiality and integrity, likely through improper authorization or data exposure within the performance review functionality.
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.20CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/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 the installed PeopleSoft Enterprise HRMS versionAccess the PeopleSoft 'About' page (typically at /ps/About) or query the PSVERSION table in the database to retrieve the application release versionAffected if The version returned is 9.0.20 exactly
-
Confirm the EPERF module is provisionedCheck if the ePerformance (EPERF) component is present in the application by viewing installed modules in PeopleSoft Application Designer or querying for EPERF-related tables such as PS_ePerf* in the databaseAffected if The EPERF module is installed and available in the system
-
Verify if EPERF is enabled for any usersQuery the PeopleSoft security tables (PSROLEUSER, PSROLECLASS) for users assigned EPERF-related roles, or check the EPERF configuration page for active role assignmentsAffected if Any users have EPERF roles assigned or the module is configured for use
-
Review EPERF role-based access control settingsAccess the PeopleSoft Security Administrator to examine role permissions for EPERF-specific roles, particularly checking which roles can access employee performance review dataAffected if Multiple roles exist with EPERF access without proper segregation of duties or with overly permissive data access
-
Check EPERF data visibility configurationExamine the EPERF module's data permission settings and row-level security configuration to determine if unauthorized users could view or modify performance review recordsAffected if Data permission settings allow authenticated users to access performance reviews outside their proper authorization scope
Your environment is affected if Oracle PeopleSoft Enterprise HRMS version 9.0.20 is installed and the EPERF module is enabled with any user roles configured, as the vulnerability allows authenticated users to improperly access or expose performance review data.
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) from July 2012 which addresses this CVE, and review EPERF module role-based access controls and user permissions to ensure proper segregation of duties.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3113 — 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-2012-3113 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