Peoplesoft ProductsApplication · Oracle

CVE-2014-6586

MEDIUM · 5.5 CVSS v2.0 Published 2015-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable 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
Unspecified vulnerability in the PeopleSoft Enterprise HRMS component in Oracle PeopleSoft Products 9.1 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Time and Labor.

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 confidence

Unspecified vulnerability in PeopleSoft Enterprise HRMS 9.1 Time and Labor module allows remote authenticated users to affect confidentiality and integrity via unknown vectors. The vulnerability requires authentication and does not impact availability.

MitigationApply Oracle Critical Patch Update for January 2015 or subsequent security patches addressing CVE-2014-6586 for PeopleSoft Enterprise HRMS 9.1.

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 ProductsApplication
Affected:= 9.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify PeopleSoft Enterprise HRMS is installed
    Locate the PeopleSoft installation directory or check system inventory for PeopleSoft Enterprise HRMS components
    Affected if PeopleSoft Enterprise HRMS is not present on the system (not affected)
  2. Confirm the installed version is 9.1
    Use PSADMIN utility or check the version information in the PeopleSoft application server or web profile. Run 'psadmin -version' or check the version.properties file in the PS_HOME directory
    Affected if The installed version equals 9.1 (affected if Time and Labor module is in use)
  3. Verify Time and Labor module is enabled
    Check if the TL (Time and Labor) component is configured in PeopleSoft. Access Application Designer or check the database for TL_ tables and related components. Look for TL_MGR_xxx processes in Process Scheduler
    Affected if The Time and Labor module is present and configured in the environment (potential attack vector)
  4. Confirm remote web access is configured
    Check the PeopleSoft web profile configuration (webprofile.properties) and web server settings to determine if HTTP/HTTPS listeners are enabled for the application
    Affected if Remote web access is enabled and the Time and Labor module is exposed (direct exposure path exists)
  5. Check if external authentication is required
    Review the PeopleSoft sign-on page and web profile security settings to confirm that authentication is enforced. Access 'PeopleTools > Security > User Profiles' to verify authentication is required
    Affected if The vulnerability requires authenticated access, so unauthenticated-only access would not trigger this specific flaw

You are affected if PeopleSoft Enterprise HRMS version 9.1 is running with the Time and Labor module enabled and accessible via remote authenticated sessions.

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 Oracle Critical Patch Update for January 2015 or subsequent security patches addressing CVE-2014-6586 for PeopleSoft Enterprise HRMS 9.1.

Fix this in Peoplesoft Products Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6586 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-6586 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