dbcve.org
Peoplesoft Enterprise EsettlementsApplication · Oracle

CVE-2017-3570

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 FSCM component of Oracle PeopleSoft Products (subcomponent: eSettlements). The supported version that is affected is 9.1. Easily "exploitable" vulnerability allows high privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise FSCM. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise FSCM accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise FSCM 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 · high confidence

CVE-2017-3570 is a vulnerability in PeopleSoft Enterprise FSCM's eSettlements subcomponent (version 9.1). The flaw allows a high-privileged attacker with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as gain unauthorized access to sensitive or complete data within the FSCM module. The attack requires high-level privileges (PR:H), making it less exploitable than vulnerabilities affecting lower-privileged users.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for April 2017 that addresses this vulnerability, or upgrade to a patched version of PeopleSoft FSCM 9.1. Additionally, restrict network access to the PeopleSoft HTTP interfaces and limit the number of high-privileged accounts.

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 EsettlementsApplication
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
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. Identify PeopleSoft FSCM eSettlements version
    Access PeopleSoft Application Designer or use SQL query against the version tables (such as PSVERSION or release-specific tables) to determine the exact eSettlements application version installed in your environment
    Affected if The installed version is exactly 9.1 (exact match required)
  2. Confirm eSettlements module is active
    Check the PeopleSoft Fluid Home or Navigation > Set Up Financials/Supply Chain > Product Related > eSettlements to verify the module is provisioned and accessible in the FSCM system
    Affected if eSettlements module is enabled and accessible in the FSCM 9.1 environment
  3. Verify HTTP listener exposure
    Review PeopleSoft web profile configuration and web server settings (typically via PIA - PeopleSoft Internet Architecture) to determine if HTTP/HTTPS endpoints are exposed to network access
    Affected if HTTP interfaces for PeopleSoft are reachable from untrusted networks
  4. Audit high-privilege accounts
    Use PeopleSoft Security Administrator (Security > User Profile) or query PSOPRDEFN table to enumerate accounts with high-level privileges (typically Role=Admin or similar elevated access) in the FSCM system
    Affected if Multiple high-privileged (PR:H) accounts exist in the system

Your environment is affected if you are running PeopleSoft FSCM eSettlements version 9.1 with the eSettlements module enabled and HTTP network access exposed to potential attackers.

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 relevant Oracle Critical Patch Update (CPU) for April 2017 that addresses this vulnerability, or upgrade to a patched version of PeopleSoft FSCM 9.1. Additionally, restrict network access to the PeopleSoft HTTP interfaces and limit the number of high-privileged accounts.

Fix this in Peoplesoft Enterprise Esettlements Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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