CVE-2016-0564
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 · uneditedUnspecified vulnerability in the Oracle E-Business Intelligence component in Oracle E-Business Suite 11.5.10.2, 12.1.1, 12.1.2, and 12.1.3 allows remote authenticated users to affect confidentiality and integrity via unknown vectors, a different vulnerability than CVE-2016-0561.
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 confidenceUnspecified vulnerability in Oracle E-Business Intelligence component of Oracle E-Business Suite versions 11.5.10.2 through 12.1.3 allows remote authenticated users to impact confidentiality and integrity via unknown vectors related to the BI Publisher. The CVSS 5.5 indicates a network-accessible flaw requiring low-privilege authentication but not user interaction.
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= 11.5.10.2= 12.1.1= 12.1.2= 12.1.3CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Oracle E-Business Suite installationCheck for Oracle E-Business Suite processes or examine installation directories such as $ORACLE_HOME/applications/ebs or registry entries indicating E-Business Suite presenceAffected if Oracle E-Business Suite is installed and running
-
Determine E-Business Suite versionQuery the database using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the version file in $INST_TOP/ora/10.1.2/forms/init.env for 11i or the context file in $CONTEXT_FILE for R12Affected if Version matches 11.5.10.2, 12.1.1, 12.1.2, or 12.1.3
-
Confirm BI Publisher module is enabledCheck if BI Publisher (XML Publisher) is deployed and accessible: navigate to /OA_HTML/xmlpserver/ or query SELECT xml_pub_enabled FROM apps.icx_parameters; in the databaseAffected if BI Publisher module is enabled and accessible
-
Verify network accessibility and authentication requirementsTest if the BI Publisher interface is exposed over network and determine if low-privilege user accounts can access the BI Publisher functionalityAffected if BI Publisher is network-accessible and accepts authenticated sessions with low privileges
If Oracle E-Business Suite versions 11.5.10.2 through 12.1.3 are installed with BI Publisher enabled and accessible to authenticated users, the environment is likely affected by CVE-2016-0564.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability in the Oracle E-Business Intelligence component. Verify that the patch addresses this specific CVE and regression-test BI reporting functionality post-deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0564 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-0564 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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