dbcve.org
Weblogic ServerApplication · Oracle

CVE-2017-10137

CRITICAL · 10.0 CVSS v3.0 Published 2017-08-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: JNDI). Supported versions that are affected are 10.3.6.0 and 12.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. While the vulnerability is in Oracle WebLogic Server, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

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 · high confidence

CVE-2017-10137 is a critical unauthenticated remote code execution vulnerability in the JNDI subcomponent of Oracle WebLogic Server versions 10.3.6.0 and 12.1.3.0. The flaw allows remote attackers to exploit Java deserialization through crafted HTTP requests to achieve full takeover of the WebLogic Server instance.

MitigationApply the June 2017 Oracle Critical Patch Update (CPU) or upgrade to a patched WebLogic version. Implement network segmentation and restrict HTTP/HTTPs access to WebLogic administration consoles and endpoints as an interim control.

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= 12.1.3.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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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. Confirm WebLogic Server is installed
    Locate the WebLogic installation directory (typically $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver) or check for WebLogic services running on common ports (7001, 7002 for admin console, 7003-7009 for managed servers)
    Affected if WebLogic Server is installed and running on the system
  2. Identify the installed WebLogic version
    Check the version file in the installation directory: look for a file named .productVersion or VERSION.TXT in the wlserver directory, or check the WebLogic admin console login page which displays the version on the login screen
    Affected if The installed version is exactly 10.3.6.0.0 or 12.1.3.0.0
  3. Verify the JNDI and IIOP endpoints are network accessible
    Test connectivity to the WebLogic IIOP port (typically 7001+ for IIOP, or the T3 protocol port) from untrusted networks using a tool like curl or netcat, and check if the /console admin interface is reachable over HTTP/HTTPS from the network
    Affected if The admin console or IIOP/T3 ports are exposed to untrusted network segments without authentication filtering
  4. Confirm Java deserialization is enabled for the affected component
    Review the WebLogic configuration files (config.xml in the config directory) for enabled protocols and ensure that T3/IIOP serialization is not restricted, and check if the wls-wsat JAX-WS endpoint is accessible at /wls-wsat
    Affected if Java deserialization via T3/IIOP protocols or the wls-wsat endpoint is enabled and accessible to remote attackers

A system is affected if it runs Oracle WebLogic Server version 10.3.6.0.0 or 12.1.3.0.0 with exposed network interfaces allowing unauthenticated Java deserialization attacks against the JNDI subcomponent.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply the June 2017 Oracle Critical Patch Update (CPU) or upgrade to a patched WebLogic version. Implement network segmentation and restrict HTTP/HTTPs access to WebLogic administration consoles and endpoints as an interim control.

Recommended fix High confidence

For a long-term fix, upgrade to Oracle WebLogic Server 12.2.x or 14.x (latest supported version), as 10.3.6 and 12.1.3 are older versions with limited ongoing support

  1. Obtain the July 2017 Critical Patch Update (CPU) from Oracle Support: https://support.oracle.com/ (or the referenced advisory at http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html)
  2. Download the WebLogic Server patch for your specific version (10.3.6.0.0 or 12.1.3.0.0) from the July 2017 CPU
  3. Apply the patch using Oracle Smart Update (OPatch) following Oracle's standard patching procedures
  4. Restart the WebLogic Server instances after applying the patch
  5. Verify the patch was applied successfully by checking the WebLogic version and testing the JNDI endpoint
  6. Confirm the vulnerability is remediated by attempting the exploit vector (if in a non-production environment) or using Oracle's overlay diagnostic tools
Caveat When upgrading from 10.3.6/12.1.3 to 12.2.x/14.x, review application compatibility as there may be API changes, deprecated features, and configuration differences requiring code updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10137 — 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-2017-10137 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