A DHCP server, or anyone on the LAN who answers a DISCOVER first, can make the client read about a
kilobyte past the end of the received message.
The option walk keeps a pointer and an offset in step, and the only bound check uses the offset:
```c
/* addons/dhcp/nxd_dhcp_client.c:7538, 7572 */
while (i < length - 1)
{
...
size = *(++data); /* data moves 1: type -> length byte */
data += size + 1; /* data moves size + 1 more */
i += size + 1; /* i moves only size + 1 */
}
```
A TLV option occupies size + 2 bytes. `data` is advanced by size + 2 in total, `i` by size + 1, so
the offset falls one byte behind the real read position for every option the walk skips. After
enough skipped options the check `i < length - 1` still holds while `data` is already past the end
of the message, and the subsequent read of the type and length bytes comes from whatever follows.
A single OFFER carrying a long run of skippable options is enough:
```
ERROR: AddressSanitizer: heap-buffer-overflow
READ of size 1 at 0x61b000000794 thread T5
#0 _nx_dhcp_search_buffer addons/dhcp/nxd_dhcp_client.c:7541
#1 _nx_dhcp_get_option_value addons/dhcp/nxd_dhcp_client.c:7082
0x61b000000794 is located 164 bytes to the right of 1648-byte region
```
A well formed OFFER through the same path is handled normally, the client records the offer and
moves to REQUESTING, so the difference is the option layout rather than the harness.
The read runs in the DHCP client thread while the client is still unconfigured, so it happens on
every boot in reach of a hostile DHCP responder. The values read are used to configure the
interface, which is how the disclosed bytes become observable.
Advance `i` by size + 2, or derive the bound from `data` rather than keeping a second counter.
GHSA-rw53-r2p7-qgmf
A DHCP server, or anyone on the LAN who answers a DISCOVER first, can make the client read about...
https://github.com/advisories/GHSA-rw53-r2p7-qgmfA DHCP server, or anyone on the LAN who answers a DISCOVER first, can make the client read about a
kilobyte past the end of the received message.
The option walk keeps a pointer and an offset in step, and the only bound check uses the offset:
/* addons/dhcp/nxd_dhcp_client.c:7538, 7572 */
while (i < length - 1)
{
...
size = *(++data); /* data moves 1: type -> length byte */
data += size + 1; /* data moves size + 1 more */
i += size + 1; /* i moves only size + 1 */
}
A TLV option occupies size + 2 bytes. data is advanced by size + 2 in total, i by size + 1, so
the offset falls one byte behind the real read position for every option the walk skips. After
enough skipped options the check i < length - 1 still holds while data is already past the end
of the message, and the subsequent read of the type and length bytes comes from whatever follows.
A single OFFER carrying a long run of skippable options is enough:
ERROR: AddressSanitizer: heap-buffer-overflow
READ of size 1 at 0x61b000000794 thread T5
#0 _nx_dhcp_search_buffer addons/dhcp/nxd_dhcp_client.c:7541
#1 _nx_dhcp_get_option_value addons/dhcp/nxd_dhcp_client.c:7082
0x61b000000794 is located 164 bytes to the right of 1648-byte region
A well formed OFFER through the same path is handled normally, the client records the offer and
moves to REQUESTING, so the difference is the option layout rather than the harness.
The read runs in the DHCP client thread while the client is still unconfigured, so it happens on
every boot in reach of a hostile DHCP responder. The values read are used to configure the
interface, which is how the disclosed bytes become observable.
Advance i by size + 2, or derive the bound from data rather than keeping a second counter.
Click to expand
{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-102720",
"assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
"assignerShortName": "eclipse",
"dateUpdated": "2026-09-29T17:46:23.228Z",
"dateReserved": "2026-09-29T16:15:16.300Z",
"datePublished": "2026-09-29T17:46:23.228Z",
"state": "PUBLISHED"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
"shortName": "eclipse",
"dateUpdated": "2026-09-29T17:46:23.228Z"
},
"descriptions": [
{
"lang": "en",
"value": "A DHCP server, or anyone on the LAN who answers a DISCOVER first, can make the client read about a\n\n\n\nkilobyte past the end of the received message.\n\n\n\nThe option walk keeps a pointer and an offset in step, and the only bound check uses the offset:\n\n\n\n```c\n\n\n\n/* addons/dhcp/nxd_dhcp_client.c:7538, 7572 */\n\n\n\nwhile (i < length - 1)\n\n\n\n{\n\n ...\n size = *(++data); /* data moves 1: type -> length byte */\n data += size + 1; /* data moves size + 1 more */\n i += size + 1; /* i moves only size + 1 */\n\n\n}\n\n\n\n```\n\n\n\nA TLV option occupies size + 2 bytes. `data` is advanced by size + 2 in total, `i` by size + 1, so\n\n\n\nthe offset falls one byte behind the real read position for every option the walk skips. After\n\n\n\nenough skipped options the check `i < length - 1` still holds while `data` is already past the end\n\n\n\nof the message, and the subsequent read of the type and length bytes comes from whatever follows.\n\n\n\nA single OFFER carrying a long run of skippable options is enough:\n\n\n\n```\n\n\n\nERROR: AddressSanitizer: heap-buffer-overflow\n\n\n\nREAD of size 1 at 0x61b000000794 thread T5\n\n #0 _nx_dhcp_search_buffer addons/dhcp/nxd_dhcp_client.c:7541\n #1 _nx_dhcp_get_option_value addons/dhcp/nxd_dhcp_client.c:7082\n\n\n0x61b000000794 is located 164 bytes to the right of 1648-byte region\n\n\n\n```\n\n\n\nA well formed OFFER through the same path is handled normally, the client records the offer and\n\n\n\nmoves to REQUESTING, so the difference is the option layout rather than the harness.\n\n\n\nThe read runs in the DHCP client thread while the client is still unconfigured, so it happens on\n\n\n\nevery boot in reach of a hostile DHCP responder. The values read are used to configure the\n\n\n\ninterface, which is how the disclosed bytes become observable.\n\n\n\nAdvance `i` by size + 2, or derive the bound from `data` rather than keeping a second counter.",
"supportingMedia": [
{
"type": "text/html",
"base64": false,
"value": "<p>A DHCP server, or anyone on the LAN who answers a DISCOVER first, can make the client read about a</p><p>kilobyte past the end of the received message.</p><p>The option walk keeps a pointer and an offset in step, and the only bound check uses the offset:</p><p>```c</p><p>/* addons/dhcp/nxd_dhcp_client.c:7538, 7572 */</p><p>while (i < length - 1)</p><p>{</p><code> ...</code><br><code> size = *(++data); /* data moves 1: type -> length byte */</code><br><code> data += size + 1; /* data moves size + 1 more */</code><br><code> i += size + 1; /* i moves only size + 1 */</code><br><p>}</p><p>```</p><p>A TLV option occupies size + 2 bytes. `data` is advanced by size + 2 in total, `i` by size + 1, so</p><p>the offset falls one byte behind the real read position for every option the walk skips. After</p><p>enough skipped options the check `i < length - 1` still holds while `data` is already past the end</p><p>of the message, and the subsequent read of the type and length bytes comes from whatever follows.</p><p>A single OFFER carrying a long run of skippable options is enough:</p><p>```</p><p>ERROR: AddressSanitizer: heap-buffer-overflow</p><p>READ of size 1 at 0x61b000000794 thread T5</p><code> #0 _nx_dhcp_search_buffer addons/dhcp/nxd_dhcp_client.c:7541</code><br><code> #1 _nx_dhcp_get_option_value addons/dhcp/nxd_dhcp_client.c:7082</code><br><p>0x61b000000794 is located 164 bytes to the right of 1648-byte region</p><p>```</p><p>A well formed OFFER through the same path is handled normally, the client records the offer and</p><p>moves to REQUESTING, so the difference is the option layout rather than the harness.</p><p>The read runs in the DHCP client thread while the client is still unconfigured, so it happens on</p><p>every boot in reach of a hostile DHCP responder. The values read are used to configure the</p><p>interface, which is how the disclosed bytes become observable.</p><p>Advance `i` by size + 2, or derive the bound from `data` rather than keeping a second counter.</p>"
}
]
}
],
"affected": [
{
"vendor": "Eclipse Foundation",
"product": "eclipse-threadx/netxduo",
"defaultStatus": "unaffected",
"versions": [
{
"version": "0",
"status": "affected",
"versionType": "semver",
"lessThanOrEqual": "6.5.1"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"description": "CWE-125 Out-of-bounds Read",
"cweId": "CWE-125",
"type": "CWE"
}
]
}
],
"references": [
{
"url": "https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-8hj5-p46x-5h28"
}
],
"metrics": [
{
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"credits": [
{
"lang": "en",
"value": "L0stHeart",
"type": "reporter"
}
]
}
}
}