CVE-2025-4146
Published: 01 May 2025
Summary
CVE-2025-4146 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Netgear Ex6200 Firmware. Its CVSS base score is 8.7 (High).
Operationally, ranked in the top 27.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
A critical buffer overflow vulnerability designated CVE-2025-4146 affects Netgear EX6200 firmware version 1.0.3.94. The issue occurs in function sub_41940 when the host argument is manipulated, resulting in memory corruption that matches CWE-119 and CWE-120. The flaw is remotely reachable and carries a CVSS 4.0 score of 8.7 with high impact on confidentiality, integrity, and availability.
An authenticated remote attacker can supply a crafted host value to trigger the overflow, enabling arbitrary code execution or a crash of the affected device without user interaction.
Netgear was notified of the issue before public disclosure but did not respond, and the referenced advisories and technical reports provide no mitigation guidance or patch information. The associated EPSS score remains low, with a current value of 0.0070 and a peak of 0.0124.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12787
Vulnerability details
A vulnerability, which was classified as critical, was found in Netgear EX6200 1.0.3.94. Affected is the function sub_41940. The manipulation of the argument host leads to buffer overflow. It is possible to launch the attack remotely. The vendor was contacted…
more
early about this disclosure but did not respond in any way.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.