dbcve.org
E Business SuiteApplication · Oracle

CVE-2017-3515

MEDIUM · 5.4 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 →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Oracle User Management component of Oracle E-Business Suite (subcomponent: User Name/Password Management). Supported versions that are affected are 12.1.3, 12.2.3, 12.2.4, 12.2.5 and 12.2.6. Easily "exploitable" vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle User Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle User Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle User Management accessible data. CVSS 3.0 Base Score 4.7 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/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

Unauthenticated network attacker can exploit Oracle User Management via HTTP to perform unauthorized update, insert, or delete operations on user data. The attack requires human interaction from a victim (likely a CSRF attack where a legitimate user is tricked into clicking a malicious request). The vulnerability affects User Name/Password Management functionality in E-Business Suite versions 12.1.3 through 12.2.6.

MitigationApply Oracle Critical Patch Update patches for CVE-2017-3515. Implement anti-CSRF tokens and referer validation in Oracle User Management. For interim mitigation, restrict HTTP access to trusted networks and monitor for suspicious user management operations.

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
E Business SuiteApplication
Affected:= 12.1.3= 12.2.3= 12.2.4= 12.2.5= 12.2.6

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 Oracle E-Business Suite is accessible
    Attempt to access the Oracle E-Business Suite login page via HTTP or HTTPS (typically ports 8000-8009 or 443). Check for Oracle E-Business Suite login portal.
    Affected if The E-Business Suite is reachable over the network on HTTP ports.
  2. Determine E-Business Suite version
    Access the version information page or check the login page footer for version display. Common paths include /OA_HTML/AppsLogin or /login, or query the ICX_INDEX page.
    Affected if Installed version matches 12.1.3, 12.2.3, 12.2.4, 12.2.5, or 12.2.6.
  3. Confirm User Management module is enabled
    Log in as an administrator and navigate to User Management or User Name/Password Management functionality. Check if the Oracle User Management responsibility is available in the responsibility menu.
    Affected if The User Name/Password Management module is accessible and functional in the environment.
  4. Check HTTP exposure of User Management
    Verify that the E-Business Suite is accessible over unencrypted HTTP (port 80 or 8000-8009) rather than only HTTPS. Use network capture or check web server configuration.
    Affected if The application is accessible via HTTP instead of being restricted to HTTPS only.
  5. Inspect for missing CSRF protections
    Examine HTTP requests when using User Management features. Check if the requests include anti-CSRF tokens (such as OAUTHTOKEN or similar tokens) in forms for user creation, password reset, or modification operations.
    Affected if User Management requests lack anti-CSRF tokens and do not validate the Referer header.

The environment is affected if Oracle E-Business Suite versions 12.1.3 through 12.2.6 are running with the User Management module accessible over HTTP without CSRF protections.

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 patches for CVE-2017-3515. Implement anti-CSRF tokens and referer validation in Oracle User Management. For interim mitigation, restrict HTTP access to trusted networks and monitor for suspicious user management operations.

Fix this in E Business Suite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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