Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2017-3527

MEDIUM · 5.3 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Vulnerability in the PeopleSoft Enterprise PeopleTools component of Oracle PeopleSoft Products (subcomponent: Fluid Core). Supported versions that are affected are 8.54 and 8.55. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.0 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 · moderate confidence

Unauthenticated information disclosure vulnerability in PeopleSoft Enterprise PeopleTools Fluid Core component (versions 8.54 and 8.55). An attacker with network access via HTTP can read a subset of accessible data without authentication, exploiting a flaw in the Fluid Core subcomponent.

MitigationApply Oracle Critical Patch Update (CPU) April 2017 patch for CVE-2017-3527. Until patched, restrict network access to PeopleSoft interfaces and monitor for unauthorized data access attempts.

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 Enterprise PeopletoolsApplication
Affected:= 8.54= 8.55

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed PeopleTools version
    Access the PeopleSoft About page (typically via PeopleTools > About PeopleTools) or check the version.psp landing page on the web server. Compare the reported version to 8.54 or 8.55.
    Affected if Installed version is exactly 8.54 or exactly 8.55
  2. Confirm Fluid Core component is deployed
    Locate the Fluid Core application files on the PeopleSoft web server (typically under the PSHOME directory). Verify the Fluid-related servlets and handlers are present in the web application configuration.
    Affected if Fluid Core component files exist and are deployed on the instance
  3. Verify HTTP accessibility of PeopleSoft interface
    Check if the PeopleSoft web server (usually WebLogic or WebSphere) is listening on HTTP ports (commonly ports 80, 443, 8000, or 8080). Attempt to access the Fluid login page or unauthenticated endpoints remotely.
    Affected if HTTP/HTTPS ports are open to untrusted networks and accept connections
  4. Test for unauthenticated data access
    Send crafted HTTP requests to known Fluid Core endpoints (such as the Fluid Home page or component interfaces) without providing credentials. Observe if the server returns data or allows access to protected resources.
    Affected if Server responds with application data or accessible pages without authentication

Environment is affected if running PeopleTools version 8.54 or 8.55 with the Fluid Core component exposed via accessible HTTP ports that permit unauthenticated information disclosure.

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) April 2017 patch for CVE-2017-3527. Until patched, restrict network access to PeopleSoft interfaces and monitor for unauthorized data access attempts.

Fix this in Peoplesoft Enterprise Peopletools Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3527 — 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-2017-3527 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