Skip to content

CVE-2017-3506

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).

CVSS
7.4Highscored by CISA
Exploited in the wild
Yes, in CISA KEV since 3 Jun 2024CISA deadline for US federal agencies: 24 Jun 2024unvetted proof-of-concept code on github
EPSS
96.0%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
24 Apr 2017analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • oracle:weblogic_server

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.

Also consider: shlex/execve-style APIs

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 3 Jun 2024.
CISA due date
24 Jun 2024, the remediation deadline for US federal agencies
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code
Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept · 1 Nuclei template
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 28 Jun 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 24 Apr 2017Published
  2. 5 Nov 2019First proof-of-concept repository on GitHub (unvetted)924 days (about 3 years) later
  3. 3 Jun 2024Added to CISA KEV (exploited in the wild)1,672 days (about 5 years) later
  4. 24 Jun 2024CISA remediation due date (US federal agencies)21 days later
  5. 28 Jun 2024CISA SSVC assessment: exploitation active4 days later
  6. 21 Oct 2025CVE record last updated481 days (about 1 year) later
  7. 12 Nov 2026Analysed by vulneraibility.com386 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityHighNeeds specific conditions, a race or a particular configuration.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2017-3506 being exploited?

Yes. CVE-2017-3506 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2017-3506?

CVE-2017-3506 is rated High with a CVSS score of 7.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2017-3506?

Yes. A fix has been recorded for CVE-2017-3506. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2017-3506 affect?

CVE-2017-3506 affects oracle:weblogic_server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

4 references in the CVE record, grouped by the tags the record gives them.

Other links (4)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com