dbcve.org
Identity ManagerApplication · Oracle

CVE-2017-10151

CRITICAL · 10.0 CVSS v3.0 Published 2017-10-30
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Identity Manager component of Oracle Fusion Middleware (subcomponent: Default Account). Supported versions that are affected are 11.1.1.7, 11.1.2.3 and 12.2.1.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Identity Manager. While the vulnerability is in Oracle Identity Manager, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle Identity Manager. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

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 remote code execution vulnerability in Oracle Identity Manager's Default Account subcomponent. The vulnerability allows unauthenticated attackers with network access via HTTP to compromise the identity management system using default credentials or a default account that was not properly secured or disabled, leading to complete system takeover.

MitigationImmediately change or disable all default accounts/credentials in Oracle Identity Manager and apply the relevant Oracle Critical Patch Update (CPU) for CVE-2017-10151 to affected versions 11.1.1.7, 11.1.2.3, and 12.2.1.3. Restrict network access to Oracle Identity Manager interfaces as an interim control.

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
Identity ManagerApplication
Affected:= 11.1.1.7= 11.1.1.9= 11.1.2.1.0= 11.1.2.2.0= 11.1.2.3= 12.2.1.3

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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. Confirm Oracle Identity Manager is installed
    Look for Oracle Identity Manager directories (typically under $ORACLE_HOME/idm or $ORACLE_HOME/oim) or check for the 'Oracle Identity Manager' service/process running on the system.
    Affected if Oracle Identity Manager is not present on the system, the CVE does not apply.
  2. Identify the installed OIM version
    Check the Oracle Identity Manager version by locating the version file in the OIM home directory (such as $ORACLE_HOME/oim/server/bin/version.info or through the Oracle Fusion Middleware inventory). Alternatively, access the OIM console and check the 'About' page.
    Affected if The installed version matches one of the affected versions: 11.1.1.7, 11.1.1.9, 11.1.2.1.0, 11.1.2.2.0, 11.1.2.3, or 12.2.1.3.
  3. Verify if the default account is active
    Log into the Oracle Identity Manager console or query the OIM user database to enumerate accounts. Specifically check for the presence and status of default accounts that ship with OIM (such as xelsysadm or other built-in accounts).
    Affected if A default account with its original password or an unsecured default account is still enabled and accessible.
  4. Check if HTTP network access is exposed
    Determine if the Oracle Identity Manager web interface (typically on ports 7001, 7003, or 14000) is accessible from untrusted networks by reviewing firewall rules, load balancer configurations, or using a network scanning tool.
    Affected if The OIM HTTP interface is reachable from untrusted network segments or the internet without proper access controls.

The system is affected if Oracle Identity Manager is running a version matching 11.1.1.7, 11.1.1.9, 11.1.2.1.0, 11.1.2.2.0, 11.1.2.3, or 12.2.1.3 AND a default account remains active with default credentials AND the HTTP interface is network-accessible to 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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Immediately change or disable all default accounts/credentials in Oracle Identity Manager and apply the relevant Oracle Critical Patch Update (CPU) for CVE-2017-10151 to affected versions 11.1.1.7, 11.1.2.3, and 12.2.1.3. Restrict network access to Oracle Identity Manager interfaces as an interim control.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) that includes the fix for CVE-2017-10151. For definitive fixed version information, refer to the July 2017 Oracle Critical Patch Update.

  1. Navigate to Oracle Critical Patch Updates and Security Alerts: https://www.oracle.com/security-alerts/
  2. Locate the July 2017 Critical Patch Update (or the update containing CVE-2017-10151)
  3. Access My Oracle Support (https://support.oracle.com) and search for patch 26685408 or the patch specific to this CVE
  4. Download the appropriate patch for your Oracle Identity Manager version (11.1.1.7, 11.1.1.9, 11.1.2.1.0, or 11.1.2.2.0)
  5. Review the patch readme for prerequisites and installation instructions
  6. Apply the patch in a test environment first
  7. Validate the patch was applied successfully and that Oracle Identity Manager functions correctly
  8. Apply the patch to production environments
Caveat Review Oracle patch readme for any known issues or post-installation requirements. Test thoroughly in non-production before deploying to production.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Identity Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,620
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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