CVE-2019-25607
Local buffer overflow in Axessh 4.2 log filename enables arbitrary code execution.
Is CVE-2019-25607 being exploited?
Not confirmed. CVE-2019-25607 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.15% probability of exploitation in the next 30 days.
How severe is CVE-2019-25607?
CVE-2019-25607 is rated High with a CVSS score of 8.6. 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-25607?
Not known from our data. No patch reference has been recorded for CVE-2019-25607, 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-25607 affect?
CVE-2019-25607 affects Axessh 4.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2019-25607?
Patch when available; upgrade to patched Axessh version.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local code execution via log filename overflow; attacker can inject shellcode to gain SYSTEM privileges.
Patch when possible
- affected4.2
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.