Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach router web interface
-
DeliverySend /router/*.cgi request with >63-byte Basic-auth username
-
ExploitOverflow 64-byte stack buffer via strcpy() in user_ok()
-
ExecutionCrash Boa process or execute code
-
ImpactDenial of service or potential device control
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the router's Boa web server and a request to any password-protected /router/*.cgi route, supplying an HTTP Basic-auth username longer than 63 bytes to overflow the fixed 64-byte stack buffer in user_ok(). No credentials, no user interaction, and no non-default configuration are needed - the vulnerable code path is in the pre-authentication Basic-auth handling itself (PR:N/UI:N). The primary limiting factor is exposure: the attacker must be able to reach the device's HTTP management interface, so the realistic risk is far higher where the web interface is exposed to the WAN/Internet and substantially lower where it is restricted to the LAN. Affected scope is Netcore NR256CN firmware through 1.5.140116. |
| Impact | This is a genuinely high-priority flaw on the signals that are present, though it is partly a worst-case projection. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, pre-authentication condition requiring no user interaction, and the description confirms the pre-auth nature (an over-length Basic-auth username to any /router/*.cgi route). CWE-121 (stack-based buffer overflow) via unbounded strcpy() into a fixed 64-byte buffer is a classic, reliably triggerable memory-corruption pattern, which supports the low attack complexity rating. However, note a signal nuance: VC:H/VI:H/VA:H reflects the 'potentially execute code' outcome, while the description's confirmed and most reliable impact is a crash of the main Boa process (denial of service); full confidentiality/integrity compromise via code execution is stated as a possibility, not a demonstrated fact, so the H/H/H confidentiality and integrity ratings should be read as best-case-for-attacker rather than proven. Key risk-scoping data is MISSING: there is no EPSS score, no CISA KEV listing, and no explicit POC flag in the input, so widespread or active exploitation cannot be asserted. The product is a specific consumer router model (Netcore NR256CN), which constrains real-world blast radius compared to enterprise infrastructure despite the high CVSS. Net: prioritize patching/mitigation for any exposed NR256CN devices, but the absence of EPSS/KEV/POC signals means this reads as a serious latent risk rather than confirmed mass exploitation. |
| Exploit ScenarioDerived | An unauthenticated attacker who can reach the router's web management interface sends an HTTP request to a protected /router/*.cgi endpoint with an HTTP Basic-auth username longer than 63 bytes. The user_ok() function copies the oversized username via strcpy() into a 64-byte stack buffer, corrupting the stack and crashing the Boa web server (loss of management availability), with the potential for arbitrary code execution if the overflow is weaponized. Given AV:N/AC:L/PR:N/UI:N, this requires only network reachability to the web interface and no credentials or user interaction; no public exploit is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
An unauthenticated stack-based buffer overflow in the Boa web server embedded in Netcore NR256CN firmware through 1.5.140116 lets remote attackers crash the router's main Boa process - and potentially execute code - by sending an HTTP Basic-auth username longer than 63 bytes to any password-protected /router/*.cgi route. The defect lives in the pre-authentication user_ok() handler, where Basic-auth usernames are copied with unbounded strcpy() into a fixed 64-byte stack buffer, so exploitation requires no credentials and no user interaction; the practical risk is governed almost entirely by exposure, since the attacker must be able to reach the device's HTTP management interface (far more dangerous when it faces the WAN, far less so when confined to the LAN). Per available data there is no confirmed active exploitation in CISA KEV and no public exploit code identified at time of analysis, but the zero-prerequisite access path and the network-facing attack vector make this a high-priority issue for any NR256CN with an internet-reachable admin UI.
RemediationAI
No vendor-released patch version is identified in the available data, so remediation must currently rest on exposure reduction and compensating controls; consult the VulnCheck advisory (https://www.vulncheck.com/advisories/netcore-nr256cn-through-1.5.140116-pre-auth-stack-overflow-via-boa-user-ok) and the linked technical write-up for any firmware update that appears after this analysis. The single most effective control is to remove WAN reachability from the device's HTTP management interface: disable remote/WAN administration in the router's web UI and block inbound TCP 80 and 443 to the NR256CN at the upstream firewall or ISP CPE - this eliminates the attack path entirely but costs remote management, which should then be replaced by VPN-only access to a trusted LAN. Where the admin UI must be reachable from other network segments, restrict it to a dedicated management VLAN or an allow-list of trusted source addresses, since the flaw is in pre-authentication parsing and cannot be closed by changing the admin username, password, or Basic-auth settings (a long or unusual password does not help; only the username field is overflowed before validation). Because no configuration toggle disables the vulnerable user_ok() path, organizations unable to isolate the interface should treat the device as untrusted, segment it so a Boa crash or compromise cannot pivot to other assets, and monitor for repeated Boa process restarts or malformed Authorization headers as an indicator of attempted exploitation. Each network-level control carries the trade-off of reduced administrative convenience and possible breakage of any legitimate remote-management or automated configuration workflows.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is a classic CWE-121 stack-based buffer overflow in Boa, a compact open-source embedded HTTP server that ships inside many SOHO/consumer routers, including the Netcore NR256CN. Boa's user_ok() routine implements the server-side half of HTTP Basic authentication: it parses the Base64-decoded credentials presented in the Authorization header and validates the supplied username/password against the configured account. In the affected firmware, the username portion of that credential pair is copied into a fixed-size 64-byte stack buffer using strcpy() with no length validation, so any username of 63 bytes or more overruns the buffer and corrupts adjacent stack memory (saved registers, frame pointer, and potentially the return address). Because user_ok() runs as part of the pre-authentication credential check, the overflow is reached on any password-protected /router/*.cgi route before any valid session exists, which is why the assessed vector resolves to PR:N/UI:N with full confidentiality, integrity, and availability impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; vendor/CNA scoring of 9.3 under CVSS 4.0 is consistent). The overflow reliably yields a crash of the main Boa process (availability impact); conversion to reliable code execution depends on the target architecture, memory protections, and the attacker's ability to shape adjacent stack contents, which the available references present as possible rather than demonstrated. The supplied CPE cpe:2.3:a:netcore:nr256cn:*:*:*:*:*:*:*:* uses a wildcard version, so the precise affected ceiling comes from the advisory language ('through 1.5.140116') rather than from CPE metadata.
Know when Nr256Cn gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Network-reachable pre-auth strcpy overflow with no interaction gives AV:N/AC:L/PR:N/UI:N; confirmed crash sets A:H and potential code execution justifies C:H/I:H, scope unchanged.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Netcore NR256CN through 1.5.140116 contains a pre-authentication stack overflow vulnerability in the Boa web server's user_ok() function, which copies Basic-auth usernames with unbounded strcpy() calls into 64-byte stack buffers. Unauthenticated attackers can send a username longer than 63 bytes to any protected /router/*.cgi route to crash the main Boa process or potentially execute code.
Executive ViewAI
Netcore NR256CN routers running firmware through 1.5.140116 are affected by a critical web-management vulnerability that can crash or potentially compromise the device, with impact concentrated in organizations that expose the router's management interface beyond a trusted network. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, so leadership should prioritize inventory, exposure reduction, and contingency planning for any internet-facing or branch-edge units. A successful attack could disrupt connectivity, expose internal networks, or provide a foothold for further intrusion, making this a high-priority risk for teams responsible for network edge devices.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling WAN-side HTTP management, restricting the router's web interface to a trusted management VLAN or VPN, blocking inbound access to TCP/80, 443, 8080, and 8443 at the perimeter, segmenting affected Netcore NR256CN devices from critical assets, monitoring for Boa process crashes or repeated HTTP authentication failures, and planning replacement or isolation for devices that cannot be secured.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Unauthenticated attackers with network reachability to the Boa-based web management interface of a Netcore NR256CN route
Unauthenticated attackers who can reach the management interface of a Netcore NR256CN router can bypass authentication a
EUVD-2026-103003
GHSA-5769-g37j-m8jq
NVD
CVE.org
Vulnrichment
Exploit-DB