dbcve.org
Identity ManagerApplication · Oracle

CVE-2017-3553

CRITICAL · 9.9 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 →
100/100
Remediation priority · Urgent
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 Oracle Identity Manager component of Oracle Fusion Middleware (subcomponent: Rules Engine). The supported version that is affected is 11.1.2.3.0. Easily "exploitable" vulnerability allows low privileged 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 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/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

A critical vulnerability in the Oracle Identity Manager Rules Engine (version 11.1.2.3.0) allows a low-privileged attacker with network access via HTTP to execute arbitrary code and take complete control of the identity management system. The attack requires only low-level user credentials and results in full compromise of confidentiality, integrity, and availability.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2017-3553, or upgrade to a patched version of Oracle Identity Manager. If immediate patching is not possible, restrict network access to the OIM interface and monitor for unauthorized rule modifications.

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.2.3.0

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Identify Oracle Identity Manager installation version
    Locate the OIM installation directory and check for version information in deployment descriptors, about pages, or version manifest files. Common locations include the Oracle Identity Manager home directory or the admin console version display.
    Affected if The installed version is exactly 11.1.2.3.0
  2. Confirm Rules Engine component is present
    Verify the Rules Engine module is deployed and accessible within the Oracle Identity Manager installation. Check for rule-related WAR files, configuration directories, or the presence of rule management functionality in the OIM admin interface.
    Affected if Rules Engine is installed and operational in the environment
  3. Verify OIM web interface is network-accessible
    Confirm the Oracle Identity Manager console is accessible over HTTP/HTTPS from the network. Test connectivity to the OIM endpoint using a web browser or curl command from an external host.
    Affected if The OIM interface is reachable over the network
  4. Check for low-privilege user accounts
    Review user accounts in Oracle Identity Manager to determine if low-privileged or basic user accounts exist that could be used to authenticate to the Rules Engine.
    Affected if Low-privilege user accounts exist in the OIM system

The environment is affected if Oracle Identity Manager version 11.1.2.3.0 is installed, the Rules Engine component is present, and the OIM interface is network-accessible with low-privilege user accounts available for authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2017-3553, or upgrade to a patched version of Oracle Identity Manager. If immediate patching is not possible, restrict network access to the OIM interface and monitor for unauthorized rule modifications.

Recommended fix Moderate confidence

Latest available 11.1.2.x patch or upgrade to a later supported Oracle Identity Manager version as recommended by Oracle Support

  1. 1. Check Oracle's Critical Patch Update advisory for April 2017 for CVE-2017-3553 details
  2. 2. Obtain the latest Oracle Identity Manager 11.1.2.x patch from Oracle Support (MOS)
  3. 3. Apply the patch following Oracle's documented patch installation procedures
  4. 4. Verify the Rules Engine component is updated and the vulnerability is remediated
  5. 5. Test Oracle Identity Manager functionality to ensure normal operations
Caveat Review Oracle patch prerequisites and known issues before applying; test in non-production environment first

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

Fix this in Identity Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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