CVE-2016-0515
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 CRM Technical Foundation component in Oracle E-Business Suite 11.5.10.2 allows remote attackers to affect confidentiality and integrity via vectors related to BIS Common Components, a different vulnerability than CVE-2016-0514.
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 confidenceA medium-severity vulnerability in Oracle E-Business Suite 11.5.10.2 affecting the CRM Technical Foundation component's BIS Common Components. The vulnerability allows remote attackers to impact confidentiality and integrity, though the specific technical nature (injection, authentication bypass, etc.) is not disclosed.
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.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle E-Business Suite versionLocate the Oracle Applications version file typically found in $APPL_TOP/../etc or run 'adident Header $APPL_TOP/admin/adovmpub.sql' to read the version. Alternatively, access the Oracle Applications About page from the Oracle Applications Navigator or query the FND_PRODUCT_INSTALLATIONS table in the database.Affected if The installed version is exactly 11.5.10.2
-
Verify CRM Technical Foundation componentQuery the FND_ORACLE_COMPONENTS view or check the Oracle Applications Manager (OAM) for installed components. Look for 'CRM Technical Foundation' in the component list.Affected if CRM Technical Foundation component is listed as installed
-
Confirm BIS Common Components moduleCheck the installed modules via Oracle Applications Manager or query the FND_MESSAGES table for BIS-related packages. Also verify the presence of BIS common component directories under $APPL_TOP.Affected if BIS Common Components (BISCC) module is present and enabled in the installation
-
Check application context for BIS configurationExamine the Oracle Applications context file (CONTEXT_NAME.xml in $APPL_TOP/admin) for BIS-related configuration entries. Look for bis_ or biscc_ configuration parameters.Affected if BIS-related context variables are configured and the site is running Oracle E-Business Suite 11.5.10.2
If Oracle E-Business Suite version 11.5.10.2 is installed with the CRM Technical Foundation and BIS Common Components enabled, the environment is affected by CVE-2016-0515.
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's relevant security patches for E-Business Suite 11.5.10.2, specifically the Oracle Critical Patch Update that addresses CVE-2016-0515. Review Oracle's advisory for affected component versions and test thoroughly in a non-production environment before deployment.
- Consultation8.0 h
- Implementation12.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 $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0515 — 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-0515 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