Any host on the LAN can send two mDNS records and make the responder write past the end of its ...
Summary
Out-of-bounds write reported (CVE-2026-102715). Risk of unauthorized operations or information disclosure. Exploitable via _nx_mdns_packet_rr_add.
Original description
The description as published by the source.
Any host on the LAN can send two mDNS records and make the responder write past the end of its
transmit packet.
The string table stores each name in a slot rounded up to a multiple of four:
/* addons/mdns/nxd_mdns.c:11436, 11443, 11447 */
memory_len = ((memory_len & 0xFFFFFFFC) + 8) & 0xFFFFFFFF;
...
len = *((USHORT*)(p - 2)); /* slot size, not string length */
if ((len == memory_len) && ... _nx_mdns_name_match(start, memory_ptr, memory_size) ...)
The lookup that decides whether an incoming name is already stored compares the rounded slot size,
so names of 12, 13, 14 and 15 characters share one bucket. A second name in the bucket is answered
with the pointer to the first, and the record then carries a string up to three bytes longer than
the length the caller accounted for. _nx_mdns_packet_rr_add (nxd_mdns.c:8911) sizes its only
bound check from that stale length, and _nx_mdns_name_string_encode writes the real string.
Two PTR records are enough, both ordinary mDNS responses to a _http._tcp query, with owner names
whose lengths fall in the same bucket:
==87491==ERROR: AddressSanitizer: heap-buffer-overflow
WRITE of size 1 at 0x611000000124 thread T5
#0 _nx_mdns_name_string_encode addons/mdns/nxd_mdns.c:13096
#1 _nx_mdns_packet_rr_add addons/mdns/nxd_mdns.c:8911
0x611000000124 is 0 bytes to the right of 228-byte region
The overflow is one to three bytes of attacker-influenced name data past `nx_packet_data_…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102715 has been found.
Attackers can target a specific entry point like _nx_mdns_packet_rr_add over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-102715" on the vendor's site.
CVE-2026-102715 — CWE-787
Attack surface: _nx_mdns_packet_rr_add / _nx_mdns_name_string_encode / _http._tcp / nx_packet_data_end
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds write (CWE-787) has been reported. Attackers reach the vulnerable code path via _nx_mdns_packet_rr_add.
Check the vendor advisory for the affected versions. Attack surface: _nx_mdns_packet_rr_add / _nx_mdns_name_string_encode / _http._tcp / nx_packet_data_end.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web nvd.nist.gov
- web github.com