CVE-2019-25603
SEH buffer overflow in TuneClone 2.20 enables local code execution via malicious license code.
Is CVE-2019-25603 being exploited?
Not confirmed. CVE-2019-25603 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.18% probability of exploitation in the next 30 days.
How severe is CVE-2019-25603?
CVE-2019-25603 is rated High. 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-2019-25603?
Not known from our data. No patch reference has been recorded for CVE-2019-25603, 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-2019-25603 affect?
CVE-2019-25603 affects TuneClone 2.20. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2019-25603?
Patch when available; restrict license input; apply least-privilege.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can trigger SEH/ROP overflow via license field to execute arbitrary code and gain shell access.
Patch when possible
- affected2.20
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.