Microsoft Working On Word Patch; Don't Panic Say Experts

Microsoft正在修复Word中的零日漏洞,该漏洞被用于投放特洛伊木马。尽管攻击范围有限,但引起了业界广泛关注。
部署运行你感兴趣的模型镜像
Microsoft said it's working on a fix for the zero-day vulnerability in Word that spooked security vendors last week, but likely won’t release a patch until June 13, the next regularly-scheduled monthly patch day.

The Microsoft Word bug first surfaced Friday, when numerous security companies, led by Symantec, said that an active exploit was using an unpatched vulnerability in Word 2003 and Word XP to drop a backdoor Trojan onto a limited number of PCs. Once in place, the Trojan -- which uses rootkit techniques to infiltrate code into difficult-to-detect locations on the drive -- provides the attacker with command shell access to the PC, effectively hijacking the machine.

Friday and Saturday, Microsoft acknowledged the Word bug, said it was working on a fix, and downplayed the vulnerability.

"So far, this is a very limited attack, and most of our antivirus partners are rating this as 'low,' said Stephen Toulouse, program manager for Microsoft Security Response Center (MSRC), wrote on the MSRC blog Saturday.

Friday, Toulouse said that his team was working up a patch, which had already moved into testing, and would release with the June update, "or sooner as warranted."

Microsoft's Windows Live Safety Center has been updated, added Toulouse, to detect and delete the Trojan planted by the exploit. (It does not, however, protect a PC from infection.)

Although virtually every security company and organization put out warnings of the Word flaw, including U.S. CERT, which releases warnings sparingly (only 19 so far in 2006), some seconded the MSRC's stress on the limited nature of the attack.

"The group originating these attacks does so in a very targeted fashion," said the SANS Institute's Internet Storm Center (ISC) in its latest alert. "The document is crafted to target a specific organization, containing specific elements that deal with just that one organization. If you don't work for them, you are very unlikely to ever see this."

But if so few users are at risk, why did the security industry's alarm bells ring so loudly? A pair of analysts offered different opinions.

"Actually, I think it was because it was something different than the usual suspect, Internet Explorer," said Mike Murray, director of research at vulnerability management vendor nCircle. "When a zero-day vulnerability is about something other than IE, it usually gets more attention."

Vincent Weafer, senior director of Symantec's security response group, had a different take. "For large organizations, like enterprises and government, this [kind of attack] is what they worry about. The attack implies knowledge [of the attacked organization] and intent to mine its data."

Unlike run-of-the-mill exploits, most of which gets blocked at the corporate perimeter, a targeted attack like this is, even if rare, the kind of risk that makes IT managers loose sleep. "They're really concerned about the possibility of targeted attacks," said Weafer.

Other details of the attack have surfaced since Friday, including the location of the Web site from which the Trojan is downloaded: China. "And the URL has been used for targeted attacks in the past," said Weafer.

By the Internet Storm Center's analysis, the site has been actively changing the URL's IP address to stay up and running. As of mid-day Monday, however, the site was offline or not available to TechWeb.

"If you're not on their target list, chances are you will not see an exploit till Microsoft releases a patch and the knowledge to exploit it can be derived by the hackers," concluded the ISC.

"Panic and blindly taking actions is probably the worst course of action you can take."

您可能感兴趣的与本文相关的镜像

Stable-Diffusion-3.5

Stable-Diffusion-3.5

图片生成
Stable-Diffusion

Stable Diffusion 3.5 (SD 3.5) 是由 Stability AI 推出的新一代文本到图像生成模型,相比 3.0 版本,它提升了图像质量、运行速度和硬件效率

在Linux内核开发中,`BUG_ON()` 是一个常用的宏,用于在调试过程中检测条件是否满足。如果 `BUG_ON(condition)` 中的 `condition` 为真(即条件不通过),则会触发一个内核BUG,并通常导致系统进入内核恐慌(kernel panic)状态,从而停止所有正常的操作并可能重启系统 [^1]。 具体来说,当 `BUG_ON()` 判断条件为真时,它会调用 `panic()` 函数,这将导致系统崩溃,并显示一条错误消息,包括触发BUG的文件名和行号等信息。这种机制主要用于捕捉不应该发生的编程错误,例如非法的状态或逻辑错误 [^1]。 以下是一个简单的代码示例,展示了如何在内核模块中使用 `BUG_ON()`: ```c #include <linux/module.h> #include <linux/kernel.h> static int __init my_module_init(void) { int value = 5; /* 假设我们期望value不等于5 */ BUG_ON(value == 5); /* 如果条件成立,则触发BUG */ printk(KERN_INFO "Module loaded successfully\n"); return 0; } static void __exit my_module_exit(void) { printk(KERN_INFO "Module unloaded\n"); } module_init(my_module_init); module_exit(my_module_exit); MODULE_LICENSE("GPL"); MODULE_AUTHOR("Your Name"); MODULE_DESCRIPTION("A simple module to demonstrate BUG_ON usage"); ``` 在此示例中,如果 `value` 确实等于5,则 `BUG_ON(value == 5)` 将触发,导致内核打印错误信息并进入panic状态 [^1]。 需要注意的是,在生产环境中,通常建议使用更温和的断言机制如 `WARN_ON()`,它可以产生警告而不是立即导致系统崩溃,以便于问题可以在不影响系统稳定性的情况下被记录和分析 [^1]。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值