dbcve.org
Peoplesoft Enterprise Scm Services ProcurementApplication · Oracle

CVE-2017-3525

MEDIUM · 6.5 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 →
71/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
Vulnerability in the PeopleSoft Enterprise SCM Service Procurement component of Oracle PeopleSoft Products (subcomponent: Usability). The supported version that is affected is 9.2. Easily "exploitable" vulnerability allows high privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise SCM Service Procurement. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise SCM Service Procurement accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise SCM Service Procurement accessible data. CVSS 3.0 Base Score 6.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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

Vulnerability in PeopleSoft Enterprise SCM Service Procurement's Usability subcomponent allows high-privileged attackers with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to sensitive or complete data sets. The flaw appears to be an access control or authorization bypass in the usability layer that improperly restricts high-privileged user actions.

MitigationApply the Oracle Critical Patch Update for April 2017 (or subsequent relevant patches) that addresses CVE-2017-3525. Additionally, review and restrict user role permissions in PeopleSoft to enforce least-privilege principles beyond what the patch addresses.

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 Scm Services ProcurementApplication
Affected:= 9.2

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

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 SCM version
    Access PeopleSoft Enterprise Navigator > About > About This Page, or query the PSVERSION table for the version number. Compare the installed version against the affected version (9.2).
    Affected if The installed PeopleSoft Enterprise SCM Services Procurement version is exactly 9.2.
  2. Confirm Service Procurement module is active
    Log into PeopleSoft Enterprise and navigate to Enterprise Components > Service Procurement > Service Procurement Setup, or check the PSOPTIONS table to see if Service Procurement functionality is enabled.
    Affected if Service Procurement module is installed and enabled in the PeopleSoft environment.
  3. Verify Usability subcomponent configuration
    Navigate to PeopleTools > Integration Broker > Service Configuration, or check the PS_SRVRCFG table to examine whether the Usability service subcomponent is configured and operational.
    Affected if The Usability subcomponent within Service Procurement is configured and active.
  4. Inspect high-privileged user role assignments
    Use PeopleSoft Security Navigator or query the PSROLEUSER table to list users assigned high-privileged roles such as Power User, Administrator, or procurement-specific roles like Buyer or Procurement Manager.
    Affected if Multiple high-privileged user accounts exist with network-accessible HTTP credentials.

The environment is affected if running PeopleSoft Enterprise SCM Services Procurement version 9.2 with the Service Procurement Usability subcomponent enabled and accessible via HTTP to high-privileged users.

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 the Oracle Critical Patch Update for April 2017 (or subsequent relevant patches) that addresses CVE-2017-3525. Additionally, review and restrict user role permissions in PeopleSoft to enforce least-privilege principles beyond what the patch addresses.

Fix this in Peoplesoft Enterprise Scm Services Procurement Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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