Report ManagerApplication · Oracle

CVE-2016-0539

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 Report Manager component in Oracle E-Business Suite 11.5.10.2, 12.1.3, 12.2.3, and 12.2.4 allows remote attackers to affect confidentiality 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 · moderate confidence

CVE-2016-0539 is an unspecified vulnerability in the Oracle Report Manager component of Oracle E-Business Suite versions 11.5.10.2, 12.1.3, 12.2.3, and 12.2.4. The vulnerability allows remote attackers to affect confidentiality via unknown vectors, rated CVSS 5 (MEDIUM). The exact attack vector and technical details are not publicly disclosed in the CVE description.

MitigationApply the relevant Oracle Critical Patch Update for January 2016 or later, which addresses this vulnerability in the Oracle E-Business Suite Report Manager component. 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
Report ManagerApplication
Affected:= 11.5.10.2= 12.1.3= 12.2.3= 12.2.4

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
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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
    Locate Oracle E-Business Suite installation directories (commonly under $ORACLE_HOME or in /u01, /u02, /appltop paths on Unix systems; C:\Oracle on Windows). Look for applications directory structure containing 'reports' or 'REP' in the path.
    Affected if Oracle E-Business Suite is installed on the system
  2. Determine E-Business Suite version
    Query the Oracle database backend using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the $APPL_TOP/../patch/115/sql directory for version files. Alternatively, access Oracle Applications Manager (OAM) from the web interface and check the version banner.
    Affected if The version matches 11.5.10.2, 12.1.3, 12.2.3, or 12.2.4 exactly
  3. Verify Report Manager component is enabled
    Log into Oracle Applications Manager (OAM) as a system administrator. Navigate to Oracle Application Manager > Service > Configure Concurrent Managers. Locate the Report Manager service (RPGMRW or Report Manager). Alternatively, check the FND_CONCURRENT_PROGRAMS table for reports running under the Report Manager application.
    Affected if Report Manager component is active or running on the system
  4. Check Report Manager web interface accessibility
    Access the Report Manager URL (typically /reports/rwservlet? or /reports_owa/rwservlet) via the E-Business Suite web entry point. Attempt to reach the endpoint without authentication or with valid credentials to determine if it responds.
    Affected if The Report Manager web interface is accessible from the network

You are affected if Oracle E-Business Suite with the Report Manager component is running and its version is exactly 11.5.10.2, 12.1.3, 12.2.3, or 12.2.4.

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 for January 2016 or later, which addresses this vulnerability in the Oracle E-Business Suite Report Manager component. Restrict network access to Oracle E-Business Suite interfaces where possible.

Fix this in Report Manager 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-0539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-0539 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