CVE-2016-3439
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 Wireless component in Oracle E-Business Suite 12.1.3 allows remote attackers to affect confidentiality and integrity via vectors related to Call Phone Number Page.
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 high-severity unspecified vulnerability in Oracle E-Business Suite 12.1.3's CRM Wireless component affects the Call Phone Number Page, allowing remote attackers to compromise confidentiality and integrity. The specific flaw type is not disclosed, but the CVSS 8.2 indicates a significant impact requiring urgent remediation.
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= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle E-Business Suite versionQuery the Oracle database for the applications version: SELECT release_name FROM fnd_product_groups; or check the APPL_TOP patch level using 'adident' utility.Affected if The release_name returns 12.1.3, indicating Oracle E-Business Suite 12.1.3 is installed.
-
Verify Oracle CRM Technical Foundation versionQuery the Oracle tables for the FND application version: SELECT patch_level, banner FROM dba_segments WHERE segment_name = 'FND'; or use the Oracle AD patch utility.Affected if The CRM Technical Foundation version shows 12.1.3, matching the affected version range.
-
Confirm CRM Wireless component is installed and enabledCheck if the CRM Wireless module is registered: SELECT application_name, application_id FROM fnd_application WHERE application_name LIKE '%Wireless%'; Also verify the module status in Oracle Application Manager.Affected if The CRM Wireless component is present and enabled in the Oracle E-Business Suite installation.
-
Verify access to Call Phone Number PageCheck if the '/OA_HTML/rcwphonelist.jsp' or related CRM Wireless phone page is accessible in the web tier. Query fnd_menu_entries for menu items related to 'Call Phone' functionality.Affected if The Call Phone Number Page (rcwphonelist.jsp or similar) is accessible and functional in the web interface.
A user is affected if Oracle E-Business Suite 12.1.3 with Oracle CRM Technical Foundation 12.1.3 has the CRM Wireless component enabled and the Call Phone Number Page is accessible.
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 the Oracle Critical Patch Update that addresses CVE-2016-3439 to Oracle E-Business Suite 12.1.3, specifically targeting the CRM Wireless component. Until the patch is applied, consider restricting network access to the vulnerable functionality.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3439 — 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-3439 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