Security Resilience

CVE-2023-23110

Netgear Wnr612V2 Firmware ≤ 1.0.0.3

Public PoC
Published
02 February 2023
Modified
26 March 2025
Patch / advisory
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.0059 49th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-23110 is a high-severity Download of Code Without Integrity Check (CWE-494) vulnerability in Netgear Wnr612V2 Firmware. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique PubPrn (T1216.001); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An exploitable firmware modification vulnerability was discovered in certain Netgear products. The data integrity of the uploaded firmware image is ensured with a fixed checksum number. Therefore, an attacker can conduct a MITM attack to modify the user-uploaded firmware image…

more

and bypass the checksum verification. This affects WNR612v2 Wireless Routers 1.0.0.3 and earlier, DGN1000v3 Modem Router 1.0.0.22 and earlier, D6100 WiFi DSL Modem Routers 1.0.0.63 and earlier, WNR1000v2 Wireless Routers 1.1.2.60 and earlier, XAVN2001v2 Wireless-N Extenders 0.4.0.7 and earlier, WNR2200 Wireless Routers 1.0.1.102 and earlier, WNR2500 Wireless Routers 1.0.0.34 and earlier, R8900 Smart WiFi Routers 1.0.3.6 and earlier, and R9000 Smart WiFi Routers 1.0.3.6 and earlier.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1216.001 PubPrn Stealth
Adversaries may use PubPrn to proxy execution of malicious remote files.
T1218.005 Mshta Stealth
Adversaries may abuse mshta.
T1218.010 Regsvr32 Stealth
Adversaries may abuse Regsvr32.
T1584.008 Network Devices Resource Development
Adversaries may compromise third-party network devices that can be used during targeting.
T1601 Modify System Image Defense Impairment
Adversaries may make changes to the operating system of embedded network devices to weaken defenses and provide new capabilities for themselves.
T1685 Disable or Modify Tools Defense Impairment
Adversaries may disable, degrade, or tamper with security tools or applications (e.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-63696Shared CWE-494
CVE-2023-45839Shared CWE-494
CVE-2024-30206Shared CWE-494
CVE-2026-121688Shared CWE-494
CVE-2026-125958Shared CWE-494
CVE-2026-3502Shared CWE-494
CVE-2024-45321Shared CWE-494
CVE-2023-45821Shared CWE-494
CVE-2026-13433Shared CWE-494
CVE-2025-69263Shared CWE-494

Affected Assets

netgear
wnr612v2 firmware
≤ 1.0.0.3
netgear
dgn1000v3 firmware
≤ 1.0.0.22
netgear
d6100 firmware
≤ 1.0.0.63
netgear
wnr1000v2 firmware
≤ 1.1.2.60
netgear
xavn2001v2 firmware
≤ 0.4.0.7
netgear
wnr2200 firmware
≤ 1.0.1.102
netgear
wnr2500 firmware
≤ 1.0.0.34
netgear
r8900 firmware
≤ 1.0.3.6
netgear
r9000 firmware
≤ 1.0.3.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 9 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Likely Mitigating Controls

Our mappings. 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.

addresses: CWE-494

Policies can require integrity verification of software prior to installation, reducing risks from unverified downloads.

addresses: CWE-494

Blocks installation of components lacking a valid signature, mitigating download or installation of code without integrity checks.

addresses: CWE-494

Acquisition and maintenance portions of the strategy drive requirements for integrity verification of downloaded or supplied code.

addresses: CWE-494

Mandating integrity control and approved-only changes during development prevents incorporation of code or components lacking integrity validation.

addresses: CWE-494

Supply chain protection requires integrity verification of acquired components, directly reducing insertion or tampering of malicious code during delivery.

addresses: CWE-494

Reduces exposure to code obtained without integrity verification by requiring assurance processes that confirm authenticity and absence of tampering.

addresses: CWE-494

Tamper resistance and detection commonly include integrity verification of code and firmware obtained from external sources.

addresses: CWE-494

Component authenticity requires verifying origin/integrity of acquired firmware or software, directly preventing inclusion of code without integrity checks.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

ID.RA-09 full match
blocks

Directly requires assessing authenticity/integrity of software before acquisition and use, preventing unverified downloads.

PR.DS-02 mostly match
blocks

Requires cryptographic integrity protections (signatures/hashes) for data-in-transit, covering downloaded code.

PR.PS-05 mostly match
blocks

Prevents execution of unauthorized software, blocking the outcome of an unchecked download.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's SOURCE reach (code review, static analysis) catches the canonical patterns — curl with -k, URLClassLoader without checksum, firmware update without signature verification — directly in first-party source, and RUNTIME reach (penetration testing) can observe the download behaviour; the remainder is third-party components with this weakness in binary-only form and cases where integrity verification is delegated to external configuration, neither of which the clause's programme sees.

blocks

Mandating integrity checks, digital signatures, and origin tracing for ICT components directly reduces the chance that code or firmware lacking an integrity check will be accepted into the organisation’s environment.

blocks

A.8.20's network controls (encryption of data in transit per (e), firewalls/filtering per (i), disabling vulnerable protocols per (n)) block some attack vectors for CWE-494 — in-transit modification and unauthorized access to update servers — but the root weakness (the product not verifying integrity of downloaded code) remains, so an attacker who bypasses network controls (e.g., compromises a legitimate server or tricks the client) can still exploit it.

prevents

A.8.28 mandates secure coding practices (prohibiting unauthenticated web services, secure design principles, SAST) that would guide developers to verify integrity of downloaded code, but it is a practice-based control whose effect depends on fallible human implementation, consistent with the A.8.28 -> CWE-502 and A.8.28 -> CWE-79 anchors graded at the same rung.

prevents

A.8.30 contracts the supplier for secure design, coding and testing practices (8.25-8.29), which carry the preventive effect on this ordinary software weakness; the clause's own mechanism is contractual, so its reach is mediated and fallible in the same way the owner graded A.8.30 -> CWE-134.

blocks

A.8.7's malware detection and repair software (guidance f) scans data received over networks and downloads for known malware before use, which blocks some exploitation of CWE-494 by catching malicious payloads in transit. However, the underlying weakness — the product's own lack of integrity verification on downloaded code — remains present and exploitable by zero-day or signature-evading malware, and by adversary-in-the-middle substitution of legitimate-looking updates, which signature-based scanning does not reach.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (1 rule)
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
Oracle Linux 9 (1 rule)
  • V-271524 OL 9 must check the GPG signature of software packages originating from external software repositories before installation. blocks CWE-494
RHEL 7 (1 rule, 1 more partial)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
RHEL 8 (1 rule)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
RHEL 9 (1 rule)
  • V-257820 RHEL 9 must check the GPG signature of software packages originating from external software repositories before installation. blocks CWE-494

References