研究人员在 rsync 中发现 6 个漏洞，其中最严重的漏洞允许攻击者通过匿名读取权限在服务器上执行任意代码。这些漏洞已在即将发布的 rsync 3.4.0 中修复。以下是漏洞详情：

1. CVE-2024-12084：堆缓冲区溢出漏洞，由于校验和长度处理不当，攻击者可越界写入。影响版本：>= 3.2.7 且 < 3.4.0。建议禁用 SHA* 支持进行缓解。

2. CVE-2024-12085：未初始化栈内容信息泄露漏洞，攻击者可通过操纵校验和长度泄露栈数据。影响版本：< 3.4.0。建议编译时使用 -ftrivial-auto-var-init=zero 缓解。

3. CVE-2024-12086：rsync 服务器可泄露客户端任意文件内容。影响版本：< 3.4.0。

4. CVE-2024-12087：路径遍历漏洞，由于 --inc-recursive 选项的符号链接验证不足，恶意服务器可写入客户端任意路径。影响版本：< 3.4.0。

5. CVE-2024-12088：--safe-links 选项绕过漏洞，导致路径遍历。影响版本：< 3.4.0。

6. CVE-2024-12747：符号链接处理中的竞争条件漏洞，可能导致信息泄露或权限提升。影响版本：< 3.4.0。

建议用户尽快升级到 rsync 3.4.0 以修复这些漏洞。

https://kb.cert.org/vuls/id/952657

#网络安全 #漏洞 #rsync #CVE
#AIGC

I actually worked at the same place as Andrew Tridgell, over a quarter-century ago. I got to know a few of the OzLabs folks during their immediate post-IBM years, and always had the highest respect for them in that way where you feel acute impostor syndrome when they're in the room.

Tridge almost walked backwards into implementing the Windows SMB protocol (he was just debugging some funny NetBIOS extensions IIRC). But his paper on the #rsync algorithm was groundbreaking, and actually writing the tool to implement it was brilliant. It's become one of those tools like #curl that just forms one of the major structural supports of the modern Internet. I still remember the day that the SSH transport became the default, and I remember being able to thank him in person when he came to the San Francisco office (although IIRC by that point he'd handed control of rsync over to mbp).

I remember at my next job he came to a summit of folks working on print driver/spooler software. When he pointed out that some problems were effectively a cache-consistency algorithm, we all kind of put our fingers to our temples and said "Oh wow, you're SO right!" He was always insightful and sharp, while being gentle and approachable.

I write in the past tense because I haven't crossed paths with him in two decades, and only know what I see him put out. A friend of mine in Australia noted that he hasn't posted to the Canberra LUG list since 2020, thanking someone for congratulating him on receiving the Medal of the Order of Australia. He's very much alive, but from what little I see I grow concerned for him.

In 2024 he took over maintenance of rsync once more. The 3.3.0 release was the last one from the previous maintainer, and Tridge is currently working on 3.4.x releases.

Well... Tridge and #Claude, it seems: https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390

The issue tracker for rsync has recently lit up with regressions, showing features that worked reliably for almost 30 years are suddenly coming crashing down in 3.4.2 and 3.4.3. People are scrambling to find ways to pin rsync to known-good versions. The considerate, incisive mind I briefly knew is letting the stochastic parrots do his work for him, and it just seems so astonishingly *unlike* the person I met back in the day.

I am still willing to give him the benefit of the doubt. I hope all is well for him, but I will not cast aspersions on his goals or his abilities. No, instead I draw this conclusion:

If TRIDGE of all people can't handle #LLMs without a slopocalypse, no one can.

That means you. That means someone you admire who is intelligent and careful and considerate. Not even someone whose opinions on technology you respect a great deal.

No one.

https://teh.entar.net/@spacehobo/116659545246426837