CVE-2016-3437
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 Person Address 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 confidenceAn unspecified vulnerability in Oracle E-Business Suite 12.1.3's CRM Wireless component (Person Address Page) allows remote attackers to impact confidentiality and integrity. The nature is likely an access control or authorization flaw in the address page that permits unauthorized access or manipulation of person address data.
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.
-
Verify Oracle E-Business Suite versionQuery the Oracle applications version table (FND_PRODUCT_GROUPS or similar) or use the AD administration utilities to confirm the E-Business Suite release is 12.1.3Affected if The installed E-Business Suite version is exactly 12.1.3
-
Confirm Oracle CRM Technical Foundation versionCheck the version of the Oracle CRM Technical Foundation module using the Oracle Applications Manager (OAM) or by querying the FND_ORACLE_USERID and FND_PRODUCT_RELEASES tablesAffected if The CRM Technical Foundation version equals 12.1.3
-
Determine if CRM Wireless component is enabledUse Oracle Applications Manager or query the FND_APPLICATION and FND_RESPONSIBILITY tables to check if the CRM Wireless module/application is installed and enabledAffected if CRM Wireless component is enabled and accessible in the affected environment
-
Inspect Person Address Page access controlsReview the responsibility, function, and security definitions associated with the Person Address Page (typically under the CRM Wireless responsibility) using Oracle User Management or by checking the ICX_ADDRESS_CFU function security definitionsAffected if The Person Address Page is accessible to users without proper authorization controls or is exposed through an unrestricted responsibility
A user is affected if they are running Oracle E-Business Suite 12.1.3 with CRM Technical Foundation at version 12.1.3, have the CRM Wireless component enabled, and the Person Address Page lacks proper access controls.
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 relevant Oracle Critical Patch Update (CPU) for April 2016 or later, which includes the fix for this vulnerability in the Oracle CRM Wireless component. Verify that access controls on the Person Address Page are properly configured.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3437 — 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-3437 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