dbcve.org
MarketingApplication · Oracle

CVE-2016-0565

MEDIUM · 5.0 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 →
59/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 Marketing component in Oracle E-Business Suite 11.5.10.2, 12.1.1, 12.1.2, and 12.1.3 allows remote attackers to affect integrity via unknown vectors.

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

Vulnerability in Oracle E-Business Suite Marketing component allows remote attackers to affect integrity. The specific attack vector and technical details are not disclosed (marked as 'unspecified' by Oracle). Affects versions 11.5.10.2, 12.1.1, 12.1.2, and 12.1.3.

MitigationApply Oracle Critical Patch Update (CPU) for January 2016 or later. As an integrity-focused vulnerability, verify data integrity controls and audit Marketing module configurations. Restrict network access to Oracle E-Business Suite interfaces where possible.

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
MarketingApplication
Affected:= 11.5.10.2= 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
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/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. Identify Oracle E-Business Suite installation
    Check for Oracle E-Business Suite application servers, database components, or consult your Oracle inventory for 'Oracle E-Business Suite' installations
    Affected if Oracle E-Business Suite is present in the environment
  2. Determine E-Business Suite version
    Query the Oracle database for the version using SQL such as: SELECT release_name FROM apps.fnd_product_groups; or check the HTML landing page version header of the E-Business Suite instance
    Affected if The version matches 11.5.10.2, 12.1.1, 12.1.2, or 12.1.3 exactly
  3. Verify Marketing module is installed
    Check if the Marketing module schema is present in the database by querying dba_segments or all_tables for 'AR' or 'AS' related Marketing tables, or check the installed modules via Oracle Application Manager
    Affected if The Marketing module schema is present in the Oracle E-Business Suite instance
  4. Confirm Marketing module is enabled
    Check if the Marketing responsibility is assigned to any users via: SELECT * FROM fnd_responsibilities_vl WHERE responsibility_name LIKE '%Marketing%'; or verify the module is accessible via the E-Business Suite responsibility menu
    Affected if The Marketing responsibility is active and accessible to users

The environment is affected if Oracle E-Business Suite is installed with version 11.5.10.2, 12.1.1, 12.1.2, or 12.1.3 AND the Marketing module is present and 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 Oracle Critical Patch Update (CPU) for January 2016 or later. As an integrity-focused vulnerability, verify data integrity controls and audit Marketing module configurations. Restrict network access to Oracle E-Business Suite interfaces where possible.

Fix this in Marketing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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