dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2016-3456

HIGH · 8.2 CVSS v3.0 Published 2016-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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
Unspecified vulnerability in the Oracle Complex Maintenance, Repair, and Overhaul component in Oracle Supply Chain Products Suite 12.1.1, 12.1.2, and 12.1.3 allows remote attackers to affect confidentiality and integrity via vectors related to Dialog Box.

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

This is an unspecified vulnerability in Oracle Complex Maintenance, Repair, and Overhaul (CMRO) module affecting versions 12.1.1, 12.1.2, and 12.1.3. The vulnerability resides in the Dialog Box functionality and allows remote attackers to compromise confidentiality and integrity without impacting availability.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for April 2016 or later which contains the fix for this vulnerability. Organizations should also review Oracle's guidance for patching Oracle E-Business Suite and test thoroughly in a non-production environment before production deployment.

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
Complex Maintenance Repair And OverhaulApplication
Affected:= 12.1.1= 12.1.2= 12.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
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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. Identify Oracle E-Business Suite installation
    Query the database for the EBS release version using: SELECT release_name FROM fnd_product_groups; or check the $APPL_TOP/../admin/sql/adrelins.sql output
    Affected if The version returned is 12.1.1, 12.1.2, or 12.1.3
  2. Confirm CMRO module is installed
    Query the FND_INSTALLATIONS table or check Oracle Applications Manager (OAM) for installed modules: SELECT product_version, status FROM fnd_product_installations WHERE product_code = 'CS';
    Affected if CMRO (Customer Support) module installation shows status as 'Installed' for versions 12.1.1-12.1.3
  3. Verify Dialog Box functionality is in use
    Check the CMRO configuration for active dialog box definitions: SELECT * FROM cs_dialogs WHERE enabled_flag = 'Y'; or inspect the CMRO responsibility configuration in Oracle Forms
    Affected if Dialog Box functionality is enabled (enabled_flag = 'Y') in the CMRO module

User is affected if running Oracle E-Business Suite versions 12.1.1, 12.1.2, or 12.1.3 with the CMRO module installed and Dialog Box functionality enabled.

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 relevant Oracle Critical Patch Update (CPU) for April 2016 or later which contains the fix for this vulnerability. Organizations should also review Oracle's guidance for patching Oracle E-Business Suite and test thoroughly in a non-production environment before production deployment.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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