CVE-2016-0675
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 WebLogic Server component in Oracle Fusion Middleware 10.3.6, 12.1.2, and 12.1.3 allows remote attackers to affect confidentiality and integrity via vectors related to Console, a different vulnerability than CVE-2016-0700.
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 WebLogic Server Console component (versions 10.3.6, 12.1.2, and 12.1.3) allows remote attackers to affect confidentiality and integrity. This is a different vulnerability than CVE-2016-0700, indicating a separate weakness in the same component.
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= 10.3.6.0.0= 12.1.2.0.0= 12.1.3.0.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 installed WebLogic Server versionCheck the version file in the Oracle middleware home, typically in the registry.xml or using the WebLogic administration console about page. The version string usually appears as 10.3.6.0.0, 12.1.2.0.0, or 12.1.3.0.0 in the installation directory or startup logs.Affected if The installed version is exactly 10.3.6.0.0, 12.1.2.0.0, or 12.1.3.0.0
-
Verify the WebLogic Console application is deployedCheck if the console web application (console.war or exploded directory) exists in the domain applications folder, typically under $DOMAIN_HOME/servers/AdminServer/tmp/_WL_user/console or in the internal applications directory. Confirm the console is accessible by attempting to reach the console URL path (/console).Affected if The console application is deployed and the console URL responds with the login page or authentication prompt
-
Confirm network accessibility of the consoleReview network listener configurations in the WebLogic administration console or config.xml to determine which network interfaces and ports the AdminServer is bound to. Check if the console port (default 7001 for AdminServer) is exposed to untrusted networks by reviewing firewall rules or load balancer configurations.Affected if The console port is reachable from network segments that include untrusted or internet-facing IP addresses
If the installed WebLogic Server version is exactly 10.3.6.0.0, 12.1.2.0.0, or 12.1.3.0.0 AND the console application is deployed AND the console is network-accessible, the environment is affected by this CVE.
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 (April 2016) addressing CVE-2016-0675, or upgrade to a patched version of WebLogic Server beyond 12.1.3. Restrict console access to trusted networks if patching is delayed.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0675 — 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-0675 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