CVE-2016-3447
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 Applications Framework component in Oracle E-Business Suite 12.1.3, 12.2.3, 12.2.4, and 12.2.5 allows remote attackers to affect confidentiality and integrity via vectors related to OAF Core.
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 Applications Framework (OAF) Core allows remote attackers to impact confidentiality and integrity. The flaw affects multiple versions of Oracle E-Business Suite (12.1.3, 12.2.3-12.2.5) through the OAF component, suggesting it may be exploitable via crafted HTTP requests to OAF-based pages without authentication.
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.3= 12.2.3= 12.2.4= 12.2.5CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:H/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.
-
Confirm Oracle E-Business Suite is installedReview system inventory or consult with Oracle administrators to verify if Oracle E-Business Suite (EBS) is running in the environment. Check for Oracle HTTP Server or Oracle Application Server components that typically serve EBS applications.Affected if Oracle E-Business Suite is not present in the environment, this CVE does not apply.
-
Identify the Oracle Applications Framework versionQuery the Oracle database or consult EBS administration consoles to retrieve the OAF version. In Oracle EBS, this can often be found in the version information for the OAF core component, typically accessed through Oracle Applications Manager (OAM) or by reviewing patch level information.Affected if The installed OAF version matches 12.1.3, 12.2.3, 12.2.4, or 12.2.5 exactly.
-
Verify OAF-based pages are accessibleTest if OAF-rendered pages are reachable via HTTP/HTTPS. Common OAF page paths may include /OA_HTML/ or /OAF/ directories. Attempt to access typical OAF endpoints or review web server configuration to confirm OAF is serving pages.Affected if OAF-based pages are exposed and reachable over the network without authentication.
-
Check if OAF is enabled in the EBS environmentReview Oracle E-Business Suite configuration to determine whether the Oracle Applications Framework component is enabled. Check profile options and concurrent manager settings related to OAF functionality.Affected if OAF is enabled and active in the EBS environment, making the vulnerability surface available.
The environment is affected if Oracle E-Business Suite is running with Oracle Applications Framework versions 12.1.3, 12.2.3, 12.2.4, or 12.2.5, and OAF-based pages are accessible without authentication.
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 patches for Oracle E-Business Suite; review Oracle April 2016 CPU for specific patch identifiers and additional remediation guidance.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3447 — 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-3447 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