Riku Kato, Tatsuya Shirai, Olivier Nourry, Yutaro Kashiwa, Kenji Fujiwara, Yasutaka Kamei, Hajimu Iida · 2026 · arXiv
DOI: 10.48550/arXiv.2610.27828 · open-access PDF
O fuzzing contínuo é usado para a detecção de vulnerabilidades no software de código aberto (OSS). Serviços de grande escala, como o OSS-Fuzz do Google, confundem mais de 1.300 projetos e revelaram mais de 10.000 vulnerabilidades. Apesar disso, muitas vezes existe um atraso de tempo considerável entre quando uma vulnerabilidade é introduzida e quando é detectada (ou seja, a janela de exposição). Dado o custo computacional de fuzzing adicional, pretendemos alocar recursos de fuzzing de forma eficiente usando estimativas de risco de vulnerabilidade. Proponemos o RAISE (Risk-Aware Intensive Supplemental Execution Framework), um framework Just-In-Time (JIT).
Machine translation (Meta M2M100); the English original follows.
Continuous fuzzing is used for vulnerability detection in Open Source Software (OSS). Large-scale services such as Google's OSS-Fuzz fuzz over 1,300 projects and have revealed more than 10,000 vulnerabilities. Despite this, a considerable time lag often exists between when a vulnerability is introduced and when it is detected (i.e., the window of exposure). Given the computational cost of additional fuzzing, we aim to allocate fuzzing resources efficiently using vulnerability-risk estimates. We propose RAISE (Risk-Aware Intensive Supplemental Execution Framework), a Just-In-Time (JIT) framewor
Read in: English · Spanish · Chinese · Hindi · Arabic · Portuguese · French · German · Japanese · Russian · Korean · Indonesian · Vietnamese
GET https://store.agentexchange.work/gw/papers/verify?title=...&year=... (0.003 USD), fetch this record as JSON with /gw/papers/paper?id=2610.27828, or list what it cites with /gw/papers/references?id=.... Pay per call in USDC (x402) or with a 19 USD card key for 1,000 calls. Catalogue · llms.txtSources: OpenAlex (CC0), arXiv, Crossref. Agent Exchange