CVE-2017-3524
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 · uneditedVulnerability in the PeopleSoft Enterprise SCM Strategic Sourcing component of Oracle PeopleSoft Products (subcomponent: Bidder Registration). 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 Strategic Sourcing. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise SCM Strategic Sourcing accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise SCM Strategic Sourcing 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 confidenceCVE-2017-3524 is an authenticated vulnerability in the Bidder Registration subcomponent of PeopleSoft Enterprise SCM Strategic Sourcing version 9.2. The flaw allows a high-privileged attacker with network access via HTTP to create, delete, or modify critical data, and potentially gain unauthorized read access to sensitive information. The CVSS 3.0 score of 6.5 reflects high confidentiality and integrity impacts with no availability impact.
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= 9.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if PeopleSoft Enterprise SCM Strategic Sourcing is installedLocate the PeopleSoft installation directory or check system inventory for the presence of PeopleSoft Enterprise SCM (Supply Chain Management) with the Strategic Sourcing module.Affected if The PeopleSoft Enterprise SCM Strategic Sourcing module is present on the system.
-
Verify the installed version is 9.2Access the PeopleSoft About page or version information panel within the application, typically found under Help > About or via the PeopleTools > System Information menu. Compare the displayed version against the affected range.Affected if The installed version is exactly 9.2.
-
Confirm the Bidder Registration component is accessibleLog into the PeopleSoft application as a high-privileged user and navigate to the Strategic Sourcing module. Attempt to access the Bidder Registration functionality, typically found under Strategic Sourcing > Maintain Bidders or a similar menu path within the SCM module.Affected if The Bidder Registration subcomponent is present and accessible within the Strategic Sourcing module.
-
Check network accessibility of the PeopleSoft web tierVerify that the PeopleSoft HTTP port (usually port 80 or 443) is exposed to the network. Review web server configuration and firewall rules to determine if the application is reachable over HTTP/HTTPS from untrusted networks.Affected if The PeopleSoft application is accessible over HTTP/HTTPS from the network.
-
Review high-privileged user accessCheck the PeopleSoft security configuration to identify which users possess high-privileged roles (such as Fluid Administrator, Strategic Sourcing Administrator, or similar elevated roles) that can access the Bidder Registration component.Affected if High-privileged user accounts exist in the system who could potentially exploit this vulnerability.
Your environment is affected if you have PeopleSoft Enterprise SCM Strategic Sourcing version 9.2 running with the Bidder Registration component accessible to high-privileged users over the network.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Oracle PeopleSoft patch (refer to Oracle's April 2017 Critical Patch Update) to the affected PeopleSoft Enterprise SCM 9.2 installation. Restrict network exposure of the PeopleSoft applications to trusted users only and follow least-privilege principles for user accounts.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3524 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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