提交 #1009968: libimobiledevice fa0f79190142bc309307967c058f89c1b36eb6b8 - version 1.4.0 Memory corruption信息

标题libimobiledevice fa0f79190142bc309307967c058f89c1b36eb6b8 - version 1.4.0 Memory corruption
描述unpaired key → strdup(NULL) Location: src/afc.c:640-645 for (ptr = kvps; *ptr; ptr++) { if (!strcmp(*ptr, key)) { *value = strdup(*(ptr+1)); // no check that a value follows break; } } Root cause. Device info is a flat NUL-separated key/value list turned into a char** with a NULL sentinel. An odd list (lone key) leaves the matched key's ptr+1 pointing at the NULL sentinel → strdup(NULL) → strlen(NULL) → SIGSEGV. Trigger (peer): reply to GET_DEVINFO with body ModelNumber\0 only; victim calls afc_get_device_info_key(client, "ModelNumber", &value). Impact. Reliable NULL deref / crash (DoS). With prior Bug heap corruption, the sentinel can be attacker-influenced → arbitrary read into strdup
来源⚠️ https://bohmid-com.vercel.app/#/article/blog-afc-writeup
用户
 ahmed0000 (UID 51651)
提交2026-10-01 17時21分 (26 日前)
管理2026-10-25 18時44分 (24 days later)
状态已接受
VulDB条目426298 [libimobiledevice 直到 1.4.0 Device Info src/afc.c afc_get_device_info_key value 内存损坏]
积分20

Interested in the pricing of exploits?

See the underground prices here!