dbcve.org
Weblogic ServerApplication · Oracle

CVE-2016-0696

MEDIUM · 5.4 CVSS v3.0 Published 2016-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Unspecified vulnerability in the Oracle WebLogic Server component in Oracle Fusion Middleware 10.3.6 allows remote attackers to affect confidentiality and integrity via vectors related to Console.

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 confidence

Unspecified vulnerability in Oracle WebLogic Server Console (version 10.3.6) allows remote attackers to compromise confidentiality and integrity. The vulnerability is exploitable through the Console interface, indicating a likely injection or authentication bypass issue in the web-based administration console.

MitigationApply Oracle Critical Patch Update addressing CVE-2016-0696. If patches are unavailable, restrict network access to the WebLogic Console to trusted IPs only via network segmentation or firewall rules.

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
Weblogic ServerApplication
Affected:= 10.3.6.0.0

CVSS 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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle WebLogic Server is installed
    Look for WebLogic installation directories such as $ORACLE_HOME or common paths like /Oracle/Middleware/wlserver_10.3, C:\Oracle\Middleware\wlserver_10.3, or check for the WebLogic process (java processes with -Dweblogic.Name or containing 'weblogic' in the command line)
    Affected if WebLogic Server is not installed or the specific version is not 10.3.6.0.0, then this CVE does not apply
  2. Confirm the exact WebLogic Server version
    Check the version file in the WebLogic installation: look for a file named 'registry.xml' or 'version.ini' typically located in the wlserver_10.3 directory, or use the WebLogic Administration Console by navigating to the 'Server' -> 'Monitoring' -> 'General' page to view the version, or run: java -jar wlserver_10.3/server/lib/weblogic.jar 2>&1 | head -20
    Affected if The installed version is exactly 10.3.6.0.0 (10.3.6.0.0), then the system is affected
  3. Verify the Console interface is enabled
    Check the WebLogic configuration file (config.xml) located in the domain directory for the Console channel configuration, typically under <console-config> or <web-server> elements, or attempt to access the Console URL (typically http://hostname:7001/console or https://hostname:7002/console) in a web browser to confirm it responds
    Affected if The Console interface is enabled and accessible, the vulnerability can be exploited; if it is disabled or not configured, the attack surface may be reduced
  4. Check network exposure of the Console port
    Review firewall rules, network configuration, or WebLogic network channel settings to determine which IP addresses can reach the Console port (default 7001 for HTTP or 7002 for HTTPS), or run netstat -an | grep -E '700[12]' to list listening ports and their binding addresses
    Affected if The Console is exposed to untrusted or public network addresses (0.0.0.0 or non-restricted IP ranges), the system is at higher risk from remote exploitation

You are affected if Oracle WebLogic Server version 10.3.6.0.0 is installed AND the Administration Console interface is enabled and network-accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update addressing CVE-2016-0696. If patches are unavailable, restrict network access to the WebLogic Console to trusted IPs only via network segmentation or firewall rules.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-0696 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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