CVE-2025-4147
Published: 01 May 2025
Summary
CVE-2025-4147 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 20.0% 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 buffer overflow vulnerability exists in the Netgear EX6200 firmware version 1.0.3.94 within the function sub_47F7C. The issue is triggered by improper handling of the host argument and is tracked under CWE-119 and CWE-120. It received a CVSS 4.0 score of 8.7 and is remotely exploitable without authentication or user interaction.
An authenticated attacker with network access can supply a crafted host value to the affected function, resulting in memory corruption that may allow arbitrary code execution or a denial of service. The vendor was notified prior to disclosure but provided no response or patch.
Public references consist of a technical write-up and proof-of-concept on GitHub along with VulDB entries; no official advisory or firmware update has been issued by Netgear. The associated EPSS score remains flat at 0.0128 with no observed increase after publication.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12790
Vulnerability details
A vulnerability has been found in Netgear EX6200 1.0.3.94 and classified as critical. Affected by this vulnerability is the function sub_47F7C. The manipulation of the argument host leads to buffer overflow. The attack can be launched remotely. The vendor was…
more
contacted 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.