Peoplesoft ProductsApplication · Oracle

CVE-2013-3800

MEDIUM · 6.4 CVSS v2.0 Published 2013-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 and integrity via unknown vectors related to Business Interlinks.

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

A remote vulnerability in Oracle PeopleSoft Enterprise PeopleTools versions 8.51, 8.52, and 8.53 affecting the Business Interlinks component allows unauthenticated remote attackers to impact confidentiality and integrity. The specific attack vector is unspecified in the advisory, but Business Interlinks handles integration between PeopleSoft and external systems, suggesting potential injection or authentication bypass issues.

MitigationApply Oracle's CPU patches for CVE-2013-3800, or upgrade to a supported PeopleTools version (8.54+). If patching is not immediately feasible, restrict network access to Business Interlinks endpoints and disable the component if not required.

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

AV:N/AC:L/Au:N/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. Identify installed PeopleTools version
    Access PeopleSoft Enterprise Portal and navigate to About > Version, or query the PSVERSION table in the database for the current PeopleTools version. Alternatively, check the psadmin utility or the PeopleSoft installation logs.
    Affected if The version is 8.51, 8.52, or 8.53 specifically. Versions outside this range (including 8.54 and later) are not affected.
  2. Verify Business Interlinks component is configured
    Log into PeopleSoft Application Designer and search for Business Interlinks objects, or query the PSBCDEFN and related tables in the PeopleSoft database to check if any Business Interlink definitions exist.
    Affected if Business Interlinks definitions are present and the component is actively configured in the environment.
  3. Check Business Interlinks web endpoints are exposed
    Review web server configuration files (weblogic.xml, web.xml, or webSphere-web.xml) for servlet mappings related to Business Interlinks (typically under /servlet/psp/, //psp/, or /bc/). Use web server logs to identify access attempts to Business Interlinks URLs.
    Affected if Business Interlinks servlets are mapped and accessible via HTTP/HTTPS without requiring authentication, or are reachable from untrusted networks.
  4. Review access logs for Business Interlinks activity
    Examine web server access logs and PeopleSoft application logs for requests to Business Interlinks endpoints, particularly from unauthenticated or unexpected sources.

You are affected if your environment runs PeopleTools version 8.51, 8.52, or 8.53 AND has the Business Interlinks component enabled and accessible.

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's CPU patches for CVE-2013-3800, or upgrade to a supported PeopleTools version (8.54+). If patching is not immediately feasible, restrict network access to Business Interlinks endpoints and disable the component if not required.

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-3800 — 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-2013-3800 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