CVE-2016-20049
Stack-based buffer overflow in JAD 1.5.8e-1kali1 enables arbitrary code execution.
Is CVE-2016-20049 being exploited?
Not confirmed. CVE-2016-20049 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-2016-20049?
CVE-2016-20049 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-2016-20049?
Not known from our data. No patch reference has been recorded for CVE-2016-20049, 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-2016-20049 affect?
CVE-2016-20049 affects JAD 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-2016-20049?
Upgrade/replace JAD; avoid processing untrusted inputs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local code execution via crafted input overflowing the stack; attacker can run shellcode in app context.
Patch when possible
- affected1.5.8e-1kali1
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.