Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2017-3506: Deserialization RCE in Oracle WebLogic Server Web Services

Published Apr 24, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.4High · v3.1
EPSS96.0%100th percentile
CISA KEVYesAdded Jun 3, 2024
In the wildActivePer CISA KEV
Vendor
Oracle Corporation
IdentifiersCVE-2017-3506CWE-502

CVE-2017-3506 is a deserialization vulnerability in the Web Services subcomponent of Oracle WebLogic Server, part of Oracle Fusion Middleware. Affected supported versions are 10.3.6.0, 12.1.3.0, 12.2.1.0, 12.2.1.1, and 12.2.1.2. An unauthenticated attacker with HTTP network access can submit a specially crafted XML document to execute arbitrary operating-system commands. Successful exploitation can expose or modify critical data or all data accessible to WebLogic Server. Water Sigbin, also known as the 8220 Gang, has exploited the vulnerability in cryptocurrency-mining campaigns.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits remote operating-system command execution and unauthorized reading, creation, deletion, or modification of critical data or all data accessible to Oracle WebLogic Server. Observed campaigns have used exploitation to deploy cryptocurrency-mining malware. The available information does not establish the operating-system privileges of the executed commands.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to affected WebLogic HTTP services and apply layered security controls. Web application firewall protection can help block known exploitation patterns; Imperva Cloud WAF and on-premises WAF protection are identified as mitigating this vulnerability. Monitor for crafted XML requests and unexpected command or script execution by WebLogic processes. These controls do not replace patching.

Remediation

Patch, then assume compromise.

Apply vendor security updates addressing CVE-2017-3506 to affected Oracle WebLogic Server installations. Specific patch identifiers and fixed release versions are not available in the supplied information.

Public exploits

Exploits

No validated public exploits yet. Hidden: 3 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationOracle Weblogic Serverapplication
FAQ

Frequently asked questions

Is CVE-2017-3506 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jun 3, 2024.
Is there a public exploit for CVE-2017-3506?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2017-3506.
Is there a patch for CVE-2017-3506?
Apply vendor security updates addressing CVE-2017-3506 to affected Oracle WebLogic Server installations. Specific patch identifiers and fixed release versions are not available in the supplied information.
What products are affected by CVE-2017-3506?
Oracle Corporation Oracle Weblogic Server.
How severe is CVE-2017-3506?
CVE-2017-3506 has a CVSS v3.1 score of 7.4 (High) and an EPSS score of 96.0% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence3Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.