CVE-2019-25671
RCE in VA MAX 8.3.4 via shell injection in mtu_eth0
Is CVE-2019-25671 being exploited?
Not confirmed. CVE-2019-25671 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.66% probability of exploitation in the next 30 days.
How severe is CVE-2019-25671?
CVE-2019-25671 is rated High with a CVSS score of 8.7. 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-25671?
Not known from our data. No patch reference has been recorded for CVE-2019-25671, 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-25671 affect?
CVE-2019-25671 affects VA MAX 8.3.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2019-25671?
Patch when available; restrict access to the endpoint; monitor POSTs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can execute commands as the apache user via crafted mtu_eth0 payload in changeip.php.
Patch when possible
- affected8.3.4
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.