创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Anthropic缩短漏洞披露期限

AI 总结

据r/ClaudeAI对Anthropic Frontier Red Team政策更新的概述,自2027年1月1日起报告的漏洞将适用更短的协调披露期限。高危和严重问题将在30天后披露,其他问题为45天;若维护者未响应,Anthropic将在15天后升级至外部协调方。正在利用的漏洞仍保留7天期限,尚未经过人工审查的AI发现不适用该政策。

深度见解

该政策直接涉及Anthropic在使用Claude时发现的其他组织软件漏洞,可能改变开源维护者处理和修复漏洞的时间安排。

Anthropic's Frontier Red Team published an update to its coordinated vulnerability disclosure policy on Nov 16. This is the policy for bugs Anthropic finds in other people's software, including the ones found with Claude.

What changes: - High and critical severity issues: 90 days down to 30 before disclosure. That's a third of the time maintainers had. - All other issues: 45 days. - Escalation to an external coordinator after 15 days instead of 30, if the maintainer doesn't respond. - After a patch is out, they wait 30 days instead of 45 before sharing full technical details. - Actively exploited bugs keep the existing 7-day window.

Timing: it applies to vulnerabilities reported on or after January 1, 2027. Reports already in progress keep their old deadlines, so nothing changes today.

Their reasoning, in their words: "Models can now help develop fixes, and a bug that one model can find is increasingly likely to be found by another." A 90-day window made sense when a bug could be expected to stay private for months.

One limit: the update does not apply to AI-discovered findings that have not received human review.

The post doesn't give numbers on how many reports this covers or how long patches take today.

If you maintain an open source project, is 30 days enough to ship a fix for a critical bug, or does this only work if you also use a model to write the patch?

Source: https://www.anthropic.com/research/coordinated-vulnerability-disclosure-timelines

submitted by /u/emarkosov [link] [comments]

#Anthropic#Claude#Anthropic Frontier Red Team

原文约 1 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。