CVE-2017-20227
Buffer overflow in JAD Java Decompiler allows code execution via crafted input.
Is CVE-2017-20227 being exploited?
Not confirmed. CVE-2017-20227 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.
How severe is CVE-2017-20227?
CVE-2017-20227 is rated Critical with a CVSS score of 9.3. 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-20227?
Not known from our data. No patch reference has been recorded for CVE-2017-20227, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2017-20227 affect?
CVE-2017-20227 affects JAD Java Decompiler 1.5.8e-1kali1 and earlier. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2017-20227?
Upgrade or replace tool
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via stack-based overflow in jad command; attacker could spawn a shell.
Patch when possible
- affected1.5.8e
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.