dbcve.org
Peoplesoft ProductsApplication · Oracle

CVE-2013-5836

MEDIUM · 5.0 CVSS v2.0 Published 2013-10-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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 PeopleTools component in Oracle PeopleSoft Products 8.51, 8.52, and 8.53 allows remote attackers to affect confidentiality via unknown vectors related to Business Interlink.

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 · low confidence

CVE-2013-5836 is an unspecified vulnerability in the Business Interlink component of Oracle PeopleSoft Enterprise PeopleTools versions 8.51, 8.52, and 8.53. The vulnerability allows remote unauthenticated attackers to impact confidentiality via unknown vectors, with a CVSS base score of 5 (Medium).

MitigationApply Oracle Critical Patch Update (CPU) patches for January 2013 or later, which contain the fix for this vulnerability. For long-term remediation, upgrade to a supported PeopleTools version as 8.51-8.53 are end-of-life. Network segmentation and restricting external access to PeopleSoft portals can reduce exposure until patching is complete.

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:= 8.51= 8.52= 8.53

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
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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 checks

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

  1. Identify PeopleTools version
    Log into PeopleSoft Application Designer or check the PeopleTools homepage. The version is displayed in the 'About PeopleTools' dialog (usually accessible via Help > About PeopleTools). Alternatively, query the PSVERSION table in the database for the current tools release.
    Affected if The installed PeopleTools version is 8.51, 8.52, or 8.53 exactly as listed in the affected versions.
  2. Confirm Business Interlink component is present
    Check if the Business Interlink component is installed and accessible. In PeopleSoft, navigate to PeopleTools > Business Interlinks > Define Business Interlink. If the menu option exists and loads, the component is present in the environment.
    Affected if The Business Interlink menu path is accessible and the component exists in the PeopleSoft application.
  3. Verify network exposure
    Determine if the PeopleSoft web portal is accessible from external networks (non-internal IP ranges). Check web server configuration, load balancer rules, or firewall policies that govern access to the PeopleSoft HTTP/HTTPS ports.
    Affected if The PeopleSoft portal is reachable from untrusted networks or the internet without proper network segmentation.
  4. Check for existing patches
    Review Oracle Support documentation or the installed patch level. Query the Oracle database for applied patches related to the January 2013 CPU, or check the patch inventory in Oracle's OPatch utility if available.
    Affected if No CPU patches from January 2013 or later have been applied, and the PeopleTools version remains at 8.51, 8.52, or 8.53.

The environment is affected if running PeopleTools version 8.51, 8.52, or 8.53 with the Business Interlink component enabled and accessible, and the January 2013 CPU patch has not been applied.

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 (CPU) patches for January 2013 or later, which contain the fix for this vulnerability. For long-term remediation, upgrade to a supported PeopleTools version as 8.51-8.53 are end-of-life. Network segmentation and restricting external access to PeopleSoft portals can reduce exposure until patching is complete.

Fix this in Peoplesoft Products Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-5836 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2013-5836 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