paperbot · PL 论文追踪

全部论文 待读 收藏

P2 Protecting Source Code Privacy When Hunting Memory Bugs

在猎捕内存缺陷时保护源代码隐私
ASE 2025 40th IEEE/ACM International Conference on Automated Software Engineering (ASE)2025匹配度 2/10 · 论文聚焦源代码隐私保护与内存缺陷检测中的调试信息削减,属于程序分析和安全方向,但未涉及用户核心关注的 LLM/Agent、机器学习系统静态分析、浮点程序分析或贝叶斯程序分析。因此与研究方向匹配度较低。引用 0 inbox
Jielun Wu, Bing Shui, Hongcheng Fan, Shengxin Wu, Rongxin Wu, Yang Feng, Baowen Xu, Qingkai Shi
crossref: 2026-09-12

AI 速览

一句话:提出 DIReducer,从二进制调试信息中削减源代码信息,同时保持内存缺陷检测能力。

软件供应商在让第三方审计内存安全时,常需披露源代码,这带来知识产权泄露风险。论文提出在透明性与代码隐私间折中的方案:从非 strip 二进制中提取调试信息并尽量削减,同时保证其仍足以支持内存缺陷检测。DIReducer 包含选择性剪枝与类型最小化,后者被证明为 NP-hard,并通过归约到集合覆盖问题获得近似最优解。实验表明,该方法可减少约 95% 调试信息,而缺陷检测能力与使用完整调试信息或源代码相近。

问题
第三方内存缺陷检测通常要求供应商披露源代码或完整调试信息,导致专有算法和商业秘密面临知识产权风险。
方法
提出 DIReducer,对非 strip 二进制中的调试信息进行选择性剪枝,并通过归约到集合覆盖的类型最小化保留检测内存缺陷所需信息。
评估
在真实系统上比较削减调试信息、完整调试信息与源代码下的内存缺陷检测效果,显示可削减约 95% 信息且检测能力相近。
原文摘要(Abstract)

When proving to a third party that a software system is free from critical memory bugs, software vendors often face the problem of having to reveal their source code, so that the third party can scan the source code using static analysis tools. However, such transparency poses a significant threat to vendors, as the source code typically contains proprietary algorithms, core technical innovations, or trade secrets, exposing them to potential intellectual property risks. In this paper, we present a solution that offers a balance between transparency and code privacy, allowing software vendors to provide minimal source code information while justifying the sufficiency of bug detection. To this end, we propose DIReducer, which reduces source code information, a.k.a. debug information, from non-stripped binaries while preserving its utility for memory bug detection. DIReducer consists of two components: selective pruning and type minimization. The former eliminates redundant debug information, and the latter is proven to be NP-hard and minimizes type-related debug information by reducing it to the classic set-cover problem, which offers a near-optimal solution. Experimental results show that we can reduce 95% of debug information while maintaining similar bug detection capability compared to using full debug information or the source code.

链接与引用

DOI 原文 ·

BibTeX
@inproceedings{paperbot9228,
  title = {Protecting Source Code Privacy When Hunting Memory Bugs},
  author = {Jielun Wu and Bing Shui and Hongcheng Fan and Shengxin Wu and Rongxin Wu and Yang Feng and Baowen Xu and Qingkai Shi},
  booktitle = {ASE},
  year = {2025},
  doi = {10.1109/ase63991.2025.00107}
}