dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 29 Sep 2022.
Weblogic ServerApplication · Oracle

CVE-2018-2628

CRITICAL · 9.8 CVSS v3.1 Published 2018-04-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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: WLS Core Components). Supported versions that are affected are 10.3.6.0, 12.1.3.0, 12.2.1.2 and 12.2.1.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3 to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.0 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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

Deserialization vulnerability in Oracle WebLogic Server's T3 protocol allows unauthenticated remote code execution. Attackers send specially crafted Java objects via the T3 network protocol to achieve full server takeover without credentials.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2018-2628, disable the T3 protocol if not required, or upgrade to a patched WebLogic version.

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= 12.2.1.2.0= 12.2.1.3

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify if Oracle WebLogic Server is installed
    Check for WebLogic installation directories (typically under $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver) or look for WebLogic-specific processes (java processes with -Dweblogic.Name or similar arguments)
    Affected if WebLogic Server is found on the system
  2. Determine the installed WebLogic version
    Check the inventory file (inventory.xml or registry.xml) in the WebLogic installation directory, or run: java -jar wlserver_*.jar -invPtrLoc /var/opt/oracle/oraInst.loc -printVersion. Alternatively, check the README.txt in the wlserver directory
    Affected if Version matches 10.3.6.0.0, 12.1.3.0.0, 12.2.1.2.0, or 12.2.1.3.0
  3. Verify if T3 protocol is enabled
    Check the WebLogic Server configuration files (config.xml) for Network Access Points or IIOP/T3 configuration. In the WebLogic Administration Console, navigate to Servers > [server name] > Protocols to see if T3/IIOP are enabled
    Affected if T3 protocol is enabled and listening on the network
  4. Confirm if administration port is network-accessible
    Test connectivity to the default WebLogic administration port (default is 7001 for console, 7002 for SSL) using telnet or nc: nc -zv target 7001. Check firewall rules and network ACLs for inbound access to these ports
    Affected if The administration port is accessible from untrusted networks or the internet
  5. Check for signs of exploitation attempts
    Review WebLogic access logs (access.log) and security audit logs for patterns involving serialized Java objects, especially requests to the /wls-wsat/ coordinator endpoint or T3 protocol traffic from unknown sources
    Affected if Suspicious deserialization patterns or known exploit signatures are found in logs

A system is affected if it runs Oracle WebLogic Server version 10.3.6.0, 12.1.3.0, 12.2.1.2, or 12.2.1.3 with the T3 protocol enabled and accessible, allowing unauthenticated remote attackers to deserialize malicious Java objects.

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 Oracle Critical Patch Update (CPU) for CVE-2018-2628, disable the T3 protocol if not required, or upgrade to a patched WebLogic version.

Recommended fix High confidence

12.2.1.4 (or later)

  1. Download and apply the Oracle Critical Patch Update (CPU) for October 2018, which contains the fix for CVE‑2018‑2628 (see Oracle support document 2394525.1 for the specific patch IDs for each affected version).
  2. After installing the patch, restart all WebLogic Server instances so the deserialization fix takes effect.
  3. Alternatively, upgrade to Oracle WebLogic Server 12.2.1.4 (or a later supported release) which includes the CVE‑2018‑2628 remediation.
  4. If immediate patching or upgrading is not possible, disable the T3 and IIOP protocols in the WebLogic Administration Console (Domain → Protocols → T3/IIOP) or restrict network access to the T3 port to prevent unauthenticated remote exploitation.
Caveat Upgrading to 12.2.1.4 may require compatibility testing of existing applications and configurations; ensure custom modules, JDBC data sources, and any deprecated APIs work with the new version.

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

Fix this in Weblogic Server Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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