最新资讯
dev.to 如何在专用 GPU 服务器上用 OpenAI 兼容 API 部署 LLM dev.to 审计 153 份 Claude Code 与 Codex 会话记录:User-Agent 与 URL 中的邮箱泄露 dev.to 你的 Agent Harness 应具备的 17 项能力 dev.to 离线 AI 记忆中 0.8 余弦阈值为何失效 dev.to Kimi K3.1 Pro 开放权重:自托管 2.8T 模型前的开发者清单 dev.to 如何通过工具调用引导模型以提升 Harness 质量 dev.to AI Agent 审计轨迹不等于对话记录 dev.to 精简 MCP server 工具数量:更少工具、更小影响面,双重收益 dev.to 为什么 git checkout 无法撤销 AI 编码 agent 的改动? wechat AI短剧门槛降降降!实测即梦短剧工作室:剧本分镜预演一条龙,伙伴计划长期护航 dev.to 让模型改写文档前,先量化事实保真度 dev.to 回放 153 个 Claude Code 与 Codex 会话,审计 Agent 的生产影响范围
多元动态
登录 注册
行业动态 arxiv.org · @Ian Molloy

历史即检测器:端到端执行CVE补丁历史

原文 我的收藏

提出BUGSTONE-E2E框架,从已验证的修复提交中挖掘可复用规则,并通过漏斗式流程进行漏洞检测,利用CVE历史和CWE分类,提高检测效率。

AI推荐理由 提出BUGSTONE-E2E框架,将CVE补丁历史转化为可执行检测规则,用于代码漏洞检测,具有实际安全应用价值,但属于特定领域。

80

正文

计算机科学 > 密码学与安全 arXiv:2609.05335v1 (cs) [2026年9月4日提交] 标题:历史即检测器:端到端执行CVE补丁历史 作者:Qiushi Wu, Kevin Eykholt, Youngja Park, Xiaokui Shu, Dhilung Kirat, Douglas Lee Schales, Ian Molloy 查看论文《历史即检测器:端到端执行CVE补丁历史》的PDF,作者为Qiushi Wu等7人 查看PDF HTML(实验性) 摘要:公开漏洞数据库收集了已知软件缺陷的丰富信息,包括其弱点类型、受影响组件和相关补丁。修复提交提供了消除这些缺陷的确切代码更改。虽然这些记录捕捉了原始代码不安全的原因,但它们主要是为人工检查而记录的,而非自动化复用。因此,相同的不安全条件可能仍存在于代码的其他地方,而没有已知的公告,导致大量检测知识未被利用。 我们提出了BUGSTONE-E2E,一个将漏洞历史转化为可执行检测规则并验证其发现的框架。首先,BUGSTONE-E2E从经过验证的修复提交中挖掘可复用规则,捕获扫描锚点、修复语义和CVE来源,并按CWE和语言进行组织。其次,检测遵循漏斗形流水线:早期阶段使用轻量级分析处理大量候选,后期阶段对不断缩小的目标集应用能力更强、成本更高的模型。具体来说,BUGSTONE-E2E首先使用Tree-sitter枚举与规则锚点匹配的调用点,然后使用轻量级启发式方法(无需LLM调用)移除良性站点。接下来,基于LLM的代理在规则指导下检查剩余候选。在此检查之后,系统对幸存的候选进行重新分类并构建运行时验证,然后生成通过双向差异测试验证的范围检查补丁。使用2022年至2026年的19,325个高严重性CVE,BUGSTONE-E2E识别出2,710个修复提交,并构建了覆盖56个CWE家族的1,033条检测规则,打包成172项技能。当应用于14个程序时,它为644个发现生成了运行时证据。这些结果表明,CVE历史可以转化为可执行的工作流,将过去的漏洞转化为可复现的检测和修复。 主题: 密码学与安全 (cs.CR);人工智能 (cs.AI);软件工程 (cs.SE) 引用为: arXiv:2609.05335 [cs.CR] (或 arXiv:2609.05335v1 [cs.CR] 用于此版本) https://doi.org/10.48550/arXiv.2609.05335 聚焦了解更多 arXiv发布的DOI(通过DataCite,待注册) 提交历史 来自:Qiushi Wu [查看电子邮件] [v1] 2026年9月4日星期五 16:40:22 UTC (116 KB) 全文链接: 访问论文: 查看论文《历史即检测器:端到端执行CVE补丁历史》的PDF,作者为Qiushi Wu等7人 查看PDF HTML(实验性) TeX源 查看许可证 当前浏览上下文: cs.CR 新 | 最近 | 2026-09 更改为浏览: cs cs.AI cs.SE 参考文献与引用 NASA ADS Google Scholar Semantic Scholar 导出BibTeX引用 加载中... BibTeX格式引用 × 加载中... 数据提供: 书签 书目工具 书目与引用工具 书目浏览器切换 书目浏览器(什么是浏览器?) 关联论文切换 关联论文(什么是关联论文?) Litmaps切换 Litmaps(什么是Litmaps?) scite.ai切换 scite智能引用(什么是智能引用?) 代码、数据、媒体 与本文相关的代码、数据和媒体 alphaXiv切换 alphaXiv(什么是alphaXiv?) 代码链接切换 CatalyzeX代码查找器(什么是CatalyzeX?) DagsHub切换 DagsHub(什么是DagsHub?) GotitPub切换 Gotit.pub(什么是GotitPub?) Huggingface切换 Hugging Face(什么是Huggingface?) ScienceCast切换 ScienceCast(什么是ScienceCast?) 演示 演示 Replicate切换 Replicate(什么是Replicate?) Spaces切换 Hugging Face Spaces(什么是Spaces?) Spaces切换 TXYZ.AI(什么是TXYZ.AI?) 相关论文 推荐与搜索工具 链接到Influence Flower Influence Flower(什么是Influence Flowers?) 核心推荐器切换 CORE推荐器(什么是CORE?) 作者 地点 机构 主题 关于arXivLabs arXivLabs:与社区合作者的实验项目 arXivLabs是一个框架,允许合作者直接在我们的网站上开发和分享新的arXiv功能。 与arXivLabs合作的个人和组织都接受并认可我们的开放性、社区、卓越和用户数据隐私价值观。arXiv致力于这些价值观,并且只与遵守这些价值观的合作伙伴合作。 有一个能为arXiv社区增加价值的项目想法吗?了解更多关于arXivLabs的信息。 这篇论文的哪些作者是背书人? | 禁用MathJax(什么是MathJax?)
查看原文(中文正文为 AI 翻译)
Computer Science > Cryptography and Security arXiv:2609.05335v1 (cs) [Submitted on 4 Sep 2026] Title:The History Is the Detector: Executing CVE Patch History, End-to-End Authors:Qiushi Wu, Kevin Eykholt, Youngja Park, Xiaokui Shu, Dhilung Kirat, Douglas Lee Schales, Ian Molloy View a PDF of the paper titled The History Is the Detector: Executing CVE Patch History, End-to-End, by Qiushi Wu and 6 other authors View PDF HTML (experimental) Abstract:Public vulnerability databases collect rich information about known software flaws, including their weakness types, affected components, and related patches. Fixing commits provide the exact code changes that removed these flaws. While these records capture why the original code was unsafe, they are documented mainly for human inspection rather than automated reuse. Consequently, the same unsafe conditions may still exist elsewhere in code without a known advisory, leaving much of this detection knowledge unused. We present BUGSTONE-E2E, a framework that transforms vulnerability history into executable detection rules and validates their findings. First, BUGSTONE-E2E mines reusable rules from verified fixing commits, capturing scan anchors, fix semantics, and CVE provenance and organizing them by CWE and language. Second, detection follows a funnel-shaped pipeline: early stages process a large pool of candidates using lightweight analysis, while later stages apply increasingly capable and expensive models to a shrinking set of targets. Specifically, BUGSTONE-E2E first enumerates call sites matching rule anchors using Tree-sitter, then removes benign sites using lightweight heuristics without LLM calls. Next, LLM-based agents inspect the remaining candidates guided by the rule. Following this inspection, the system re-triages surviving candidates and builds runtime verifications, then generates scope-checked patches validated via two-sided differential tests. Using 19,325 high-severity CVEs from 2022 to 2026, BUGSTONE-E2E identifies 2,710 fixing commits and constructs 1,033 detection rules across 56 CWE families, packaged into 172 skills. When applied across 14 programs, it produced runtime evidence for 644 findings. These results demonstrate that CVE history can be turned into an executable workflow, transforming past vulnerabilities into reproducible detection and repair. Subjects: Cryptography and Security (cs.CR); Artificial Intelligence (cs.AI); Software Engineering (cs.SE) Cite as: arXiv:2609.05335 [cs.CR] (or arXiv:2609.05335v1 [cs.CR] for this version) https://doi.org/10.48550/arXiv.2609.05335 Focus to learn more arXiv-issued DOI via DataCite (pending registration) Submission history From: Qiushi Wu [view email] [v1] Fri, 4 Sep 2026 16:40:22 UTC (116 KB) Full-text links: Access Paper: View a PDF of the paper titled The History Is the Detector: Executing CVE Patch History, End-to-End, by Qiushi Wu and 6 other authors View PDF HTML (experimental) TeX Source view license Current browse context: cs.CR new | recent | 2026-09 Change to browse by: cs cs.AI cs.SE References & Citations NASA ADS Google Scholar Semantic Scholar export BibTeX citation Loading... BibTeX formatted citation × loading... Data provided by: Bookmark Bibliographic Tools Bibliographic and Citation Tools Bibliographic Explorer Toggle Bibliographic Explorer (What is the Explorer?) Connected Papers Toggle Connected Papers (What is Connected Papers?) Litmaps Toggle Litmaps (What is Litmaps?) scite.ai Toggle scite Smart Citations (What are Smart Citations?) Code, Data, Media Code, Data and Media Associated with this Article alphaXiv Toggle alphaXiv (What is alphaXiv?) Links to Code Toggle CatalyzeX Code Finder for Papers (What is CatalyzeX?) DagsHub Toggle DagsHub (What is DagsHub?) GotitPub Toggle Gotit.pub (What is GotitPub?) Huggingface Toggle Hugging Face (What is Huggingface?) ScienceCast Toggle ScienceCast (What is ScienceCast?) Demos Demos Replicate Toggle Replicate (What is Replicate?) Spaces Toggle Hugging Face Spaces (What is Spaces?) Spaces Toggle TXYZ.AI (What is TXYZ.AI?) Related Papers Recommenders and Search Tools Link to Influence Flower Influence Flower (What are Influence Flowers?) Core recommender toggle CORE Recommender (What is CORE?) Author Venue Institution Topic About arXivLabs arXivLabs: experimental projects with community collaborators arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website. Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them. Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs. Which authors of this paper are endorsers? | Disable MathJax (What is MathJax?)

来源报道 · 1 篇 · 以下链接均前往原始媒体

← 返回精选动态 原文

更多内容