CVE-2017-1000353
Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution. An unauthenticated remote code execution vulnerability allowed attackers to transfer a serialized Java `SignedObject` object to the Jenkins CLI, that would be deserialized using a new `ObjectInputStream`, bypassing the existing blacklist-based protection mechanism. We're fixing this issue by adding `SignedObject` to the blacklist. We're also backporting the new HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based (i.e. Java serialization) CLI protocol, disabling it by default.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack involves sending a serialized Java object to the Jenkins CLI, which is not an HTTP request but a remoting protocol. Therefore, a web application firewall cannot filter or block this attack based on HTTP traffic.
Also consider: allow-list classes · patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2017-1000353 being exploited?
Yes. CVE-2017-1000353 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-1000353?
CVE-2017-1000353 is rated Critical with a CVSS score of 9.8. 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-1000353?
Yes. A fix has been recorded for CVE-2017-1000353. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2017-1000353 affect?
CVE-2017-1000353 affects jenkins:jenkins, oracle:communications_cloud_native_core_automated_test_suite. 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.
public exploits
Public exploit code: 1 on Exploit-DB · 1 Metasploit module · 2 GitHub proofs of concept
- CloudBees Jenkins 2.32.1 - Java Deserialization · dos · 5 May 2017
- exploit/linux/http/jenkins_cli_deserialization · exploit · excellent
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.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 2 Oct 2025 (SSVC 2.0.3).
timeline
- 5 May 2017First public exploit or proof of concept
- 29 Jan 2018Published · 270 days (about 9 months) later
- 2 Oct 2025Added to CISA KEV (exploited in the wild) · 2,802 days (about 8 years) later
- 2 Oct 2025CISA SSVC assessment: exploitation active · same day later
- 21 Oct 2025CVE record last updated · 20 days later
- 23 Oct 2025CISA remediation due date (US federal agencies) · 1 day later
- 2 Nov 2026Analysed by vulneraibility.com · 376 days (about 1 year) later
also known as
- Exploitexploit-db.com /exploits/41965/
- Linksecurityfocus.com /bid/98056
- Linkoracle.com /security-alerts/cpuapr2022.html
- Linkjenkins.io /security/advisory/2017-04-26/
- Linkpacketstormsecurity.com /files/159266/Jenkins-2.56-CLI-Deserialization-Code-Execution.html
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-1000353
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- Metasploit Framework: exploit and scanner modules
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.