dbcve.org
Application Object LibraryApplication · Oracle

CVE-2016-0576

MEDIUM · 6.4 CVSS v2.0 Published 2016-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Unspecified vulnerability in the Oracle Application Object Library component in Oracle E-Business Suite 11.5.10.2 allows remote attackers to affect confidentiality and integrity via vectors related to ICX LOVs.

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 · moderate confidence

Vulnerability in Oracle E-Business Suite 11.5.10.2 Application Object Library component allows remote attackers to impact confidentiality and integrity through ICX LOVs (List of Values) functionality. The 'unspecified' nature means Oracle provided limited technical details in their advisory.

MitigationApply the January 2016 Critical Patch Update (CPU) or subsequent security patches for Oracle E-Business Suite 11.5.10.2. If patching is not immediately feasible, restrict network access to the Oracle Application Object Library ICX components.

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
Application Object LibraryApplication
Affected:= 11.5.10.2

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/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. Confirm Oracle E-Business Suite version
    Query the Oracle database or check the application server for the exact E-Business Suite version. In Oracle Applications, you can query 'SELECT release_name FROM fnd_product_groups' or check the version shown in the About Oracle Applications page.
    Affected if The installed version is exactly 11.5.10.2 (no other versions are listed as affected)
  2. Verify Application Object Library component
    Confirm that the Application Object Library (AOL) component is installed and running. This can be verified through the Oracle Applications Manager console or by checking the registered applications.
    Affected if Application Object Library is present in the installation
  3. Check ICX LOVs functionality status
    Determine if the ICX (Interactive Checkout) LOVs feature is enabled or accessible. This functionality provides List of Values screens within the E-Business Suite. Access can be verified through the ICX Forms personalizations or by checking if ICX-related responsibilities are assigned.
    Affected if ICX LOVs functionality is enabled and accessible to users
  4. Assess network accessibility of ICX components
    Review network access controls and firewall rules surrounding the Oracle E-Business Suite application tier. Identify whether the ICX port/endpoint is exposed to untrusted networks or the internet.
    Affected if The ICX component port is accessible from untrusted network segments or the internet
  5. Review ICX responsibility assignments
    Check which responsibilities and user accounts have access to ICX-related functions. In Oracle E-Business Suite, query 'FND_RESPONSIBILITY' and 'FND_USER_RESPONSIBILITY' tables to identify users with ICX responsibilities.
    Affected if Any user responsibilities include ICX LOVs access

A user is affected if they run Oracle E-Business Suite version 11.5.10.2 with ICX LOVs functionality enabled and accessible, particularly if the ICX components are network-accessible to untrusted users.

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 January 2016 Critical Patch Update (CPU) or subsequent security patches for Oracle E-Business Suite 11.5.10.2. If patching is not immediately feasible, restrict network access to the Oracle Application Object Library ICX components.

Fix this in Application Object Library Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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