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 24 Jun 2024.
Weblogic ServerApplication · Oracle

CVE-2017-3506

HIGH · 7.4 CVSS v3.1 Published 2017-04-24
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 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: Web Services). Supported versions that are affected are 10.3.6.0, 12.1.3.0, 12.2.1.0, 12.2.1.1 and 12.2.1.2. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data as well as unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.0 Base Score 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

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-3506 is a deserialization vulnerability in the Oracle WebLogic Server WLS Web Services (wsat) subcomponent. It allows an unauthenticated remote attacker with network access via HTTP to execute arbitrary code or manipulate/delete critical data. The vulnerability stems from insecure deserialization of XML data in the Web Services annotation processing, enabling complete compromise of the WebLogic Server.

MitigationApply Oracle Critical Patch Update April 2017 (or later) to patch the vulnerable WLS wsat component. Alternatively, if the Web Services functionality is not required, disable or undeploy the WLS-wsat application to eliminate the attack surface.

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.0.0= 12.2.1.1.0= 12.2.1.2.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 WebLogic Server installation and version
    Locate the WebLogic installation directory (typically under BEA_HOME or ORACLE_HOME/middleware). Check the version file in the wlserver_10.3 or wlserver_12.1/12.2 directory, or run: java -jar wlserver_10.3/server/lib/weblogic.jar -version (adjust path for your version).
    Affected if The installed version matches 10.3.6.0.0, 12.1.3.0.0, 12.2.1.0.0, 12.2.1.1.0, or 12.2.1.2.0 exactly.
  2. Determine if WLS-wsat application is deployed
    Check the WebLogic Administration Console under Deployments, or list deployed applications via WLST: ls('/AppDeployments'). Look for an application named 'wls-wsat' or 'WebServices' in the deployment list.
    Affected if The WLS-wsat application appears in the deployed applications list and is in state 'Active' or 'Running'.
  3. Verify the vulnerable endpoint is accessible
    Send an HTTP GET request to the wsat endpoint: http://<yourserver>:<port>/wls-wsat/CoordinatorPortType. A HTTP 200 or similar response indicates the endpoint exists.
    Affected if The endpoint responds (returns any HTTP status other than 404/403), indicating the WLS-wsat web service is active and reachable.
  4. Confirm Web Services feature is enabled
    Check the config.xml file in the domain config directory for <wls:wsat> or <wls:web-service> entries. Alternatively, check the WebLogic console under Domain > Security > Advanced for Web Services enablement.
    Affected if Web Services are explicitly enabled in the domain configuration, or the wsat component shows as 'Enabled' in console.

You are affected if you run any of the listed WebLogic versions AND the WLS-wsat application is deployed and the /wls-wsat/CoordinatorPortType endpoint is accessible.

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 April 2017 (or later) to patch the vulnerable WLS wsat component. Alternatively, if the Web Services functionality is not required, disable or undeploy the WLS-wsat application to eliminate the attack surface.

Recommended fix High confidence

Oracle WebLogic Server 12.2.1.3 or later (or apply April 2017 CPU patch for 10.3.6.0/12.1.3.0 versions)

  1. 1. Identify the current Oracle WebLogic Server version by checking the installation directory or using the administration console.
  2. 2. For WebLogic Server 10.3.6.0: Apply Oracle Critical Patch Update (CPU) April 2017 or later, specifically patch for CVE-2017-3506, or upgrade to a supported later version.
  3. 3. For WebLogic Server 12.1.3.0: Apply Oracle Critical Patch Update (CPU) April 2017 or later, or upgrade to a supported later version.
  4. 4. For WebLogic Server 12.2.1.0, 12.2.1.1.0, or 12.2.1.2.0: Upgrade to WebLogic Server 12.2.1.3 or later which contains the fix for CVE-2017-3506.
  5. 5. After applying the patch or upgrade, restart the WebLogic Server instances to ensure the fix takes effect.
  6. 6. Verify the fix by checking the Oracle WebLogic Server version and confirming the vulnerability is resolved through testing or scanning.
Caveat Upgrading to 12.2.1.3 may require compatibility testing of existing applications; ensure application compatibility before production deployment

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

Fix this in Weblogic Server Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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