CVE-2026-10652

{"id": "CVE-2026-10652", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-10652", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-30T16:44:24.969113Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "vulnerabilities@zephyrproject.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.8, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 2.5, "exploitabilityScore": 2.2}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.4, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.2}]}, "affected": [{"source": "vulnerabilities@zephyrproject.org", "affectedData": [{"vendor": "zephyrproject", "product": "zephyr", "versions": [{"status": "affected", "version": "4.3.0", "lessThan": "4.3.1", "versionType": "semver"}, {"status": "affected", "version": "4.4.0", "lessThan": "4.4.1", "versionType": "semver"}], "packageName": "zephyr", "programFiles": ["subsys/net/lib/dns/dns_pack.c"], "collectionURL": "https://github.com/zephyrproject-rtos/zephyr", "defaultStatus": "unaffected"}]}], "published": "2026-06-30T17:16:20.040", "references": [{"url": "https://github.com/zephyrproject-rtos/zephyr/commit/58b46c81c6796dac4dc7391f32ba006474f94dc8", "tags": ["Patch"], "source": "vulnerabilities@zephyrproject.org"}, {"url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3jxq-xx8g-q8j2", "tags": ["Exploit", "Patch", "Vendor Advisory"], "source": "vulnerabilities@zephyrproject.org"}, {"url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-3jxq-xx8g-q8j2", "tags": ["Exploit", "Patch", "Vendor Advisory"], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "vulnerabilities@zephyrproject.org", "description": [{"lang": "en", "value": "CWE-125"}]}], "descriptions": [{"lang": "en", "value": "Zephyr's DNS resolver (subsys/net/lib/dns) parses resource records from DNS responses in dns_unpack_answer(), which validated only the fixed RR header (type, class, TTL, rdlength) and accepted any attacker-declared rdlength, including one extending past the end of the received datagram. The TXT and SRV consumers in dns_validate_record() (resolve.c) then read up to rdlength bytes (clamped only to a record-type maximum such as DNS_MAX_TEXT_SIZE, default 64, not to the packet) from the receive buffer via memcpy without their own bounds check, and pass the result to the application's resolve callback. A malicious or spoofed DNS server, an on-path attacker forging UDP DNS replies, or (with mDNS/LLMNR enabled) any LAN node can craft a truncated TXT or SRV response that causes an out-of-bounds read of adjacent receive-pool memory; the disclosed stale bytes (residual contents of prior DNS packets / uninitialized pool memory) are returned to the application as TXT/SRV record contents, an information leak, and may in some configurations cross the allocation boundary and fault, causing a denial of service. The read is bounded (~64 bytes for TXT, ~6 for SRV) and read-only (no write). The fix rejects any record whose declared rdata extends past dns_msg->msg_size at the single chokepoint in dns_unpack_answer(). Affected: v4.3.0 and v4.4.0."}, {"lang": "es", "value": "El resolvedor DNS de Zephyr (subsys/net/lib/dns) analiza registros de recursos de respuestas DNS en dns_unpack_answer(), que validaba solo la cabecera RR fija (tipo, clase, TTL, rdlength) y aceptaba cualquier rdlength declarado por el atacante, incluyendo uno que se extend\u00eda m\u00e1s all\u00e1 del final del datagrama recibido. Los consumidores TXT y SRV en dns_validate_record() (resolve.c) luego leen hasta rdlength bytes (limitado solo a un m\u00e1ximo de tipo de registro como DNS_MAX_TEXT_SIZE, predeterminado 64, no al paquete) del b\u00fafer de recepci\u00f3n a trav\u00e9s de memcpy sin su propia comprobaci\u00f3n de l\u00edmites, y pasan el resultado a la devoluci\u00f3n de llamada de resoluci\u00f3n de la aplicaci\u00f3n. Un servidor DNS malicioso o suplantado, un atacante en la ruta que falsifica respuestas DNS UDP, o (con mDNS/LLMNR habilitado) cualquier nodo de LAN puede crear una respuesta TXT o SRV truncada que causa una lectura fuera de l\u00edmites de la memoria adyacente del grupo de recepci\u00f3n; los bytes obsoletos divulgados (contenido residual de paquetes DNS anteriores / memoria de grupo no inicializada) se devuelven a la aplicaci\u00f3n como contenido de registro TXT/SRV, una fuga de informaci\u00f3n, y pueden, en algunas configuraciones, cruzar el l\u00edmite de asignaci\u00f3n y fallar, causando una denegaci\u00f3n de servicio. La lectura est\u00e1 limitada (~64 bytes para TXT, ~6 para SRV) y es de solo lectura (sin escritura). La correcci\u00f3n rechaza cualquier registro cuyo rdata declarado se extiende m\u00e1s all\u00e1 de dns_msg -> msg_size en el \u00fanico punto de estrangulamiento en dns_unpack_answer(). Afectado: v4.3.0 y v4.4.0."}], "lastModified": "2026-10-25T21:10:00.770", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "AB673835-4CCD-49A7-9873-630B9EE2C814", "versionEndIncluding": "4.4.1", "versionStartIncluding": "4.3.0"}], "operator": "OR"}]}], "sourceIdentifier": "vulnerabilities@zephyrproject.org"}