CHRONOS: Time-Aware Zero-Shot Identification of Libraries from Vulnerability Reports
Not on the map. Why?
Abstract (arXiv)
Tools that alert developers about library vulnerabilities depend on accurate, up-to-date vulnerability databases which are maintained by security researchers. These databases record the libraries related to each vulnerability. However, the vulnerability reports may not explicitly list every library and human analysis is required to determine all the relevant libraries. Human analysis may be slow and expensive, which motivates the need for automated approaches. Researchers and practitioners have proposed to automatically identify libraries from vulnerability reports using extreme multi-label learning (XML). While state-of-the-art XML techniques showed promising performance, their experiment settings do not practically fit what happens in reality. Previous studies randomly split the vulnerability reports data for training and testing their models without considering the chronological order of the reports. This may unduly train the models on chronologically newer reports while testing the models on chronologically older ones. However, in practice, one often receives chronologically new reports, which may be related to previously unseen libraries. Under this practical setting, we observe that the performance of current XML techniques declines substantially, e.g., F1 decreased from 0.7 to 0.28 under experiments without and with consideration of chronological order of vulnerability reports. We propose a practical library identification approach, namely CHRONOS, based on zero-shot learning. The novelty of CHRONOS is three-fold. First, CHRONOS fits into the practical pipeline by considering the chronological order of vulnerability reports. Second, CHRONOS enriches the data of the vulnerability descriptions and labels using a carefully designed data enhancement step. Third, CHRONOS exploits the temporal ordering of the vulnerability reports using a cache to prioritize prediction of...
Key facts. Cited by 7 papers in the map (data through 7 Oct 2026). First posted on arXiv 10 Jan 2023.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2023: 1; 2024: 1; 2025: 3; 2026: 2.
7 papers.
- 2025SecureVibeBench: Benchmarking Secure Vibe Coding of AI Agents via Reconstructing Vulnerability-Introducing Scenarioscited by 11
- 2023Multi-Granularity Detector for Vulnerability Fixescited by 4
- 2025Do Existing Testing Tools Really Uncover Gender Bias in Text-to-Image Models?cited by 4
- 2025"My productivity is boosted, but ..." Demystifying Users' Perception on AI Coding Assistantscited by 4
- 2024LEGION: Harnessing Pre-trained Language Models for GitHub Topic Recommendations with Distribution-Balance Losscited by 1
- 2026DepRadar: Agentic Coordination for Context Aware Defect Impact Analysis in Deep Learning Librariescited by 0
- 2026Athena: Vulnerability-Affected Library Identification via Knowledge Graph Completioncited by 0
- 2026Athena: Vulnerability-Affected Library Identification via Knowledge Graph Completion1 Sep 2026
- 2026DepRadar: Agentic Coordination for Context Aware Defect Impact Analysis in Deep Learning Libraries14 Jan 2026
- 2025SecureVibeBench: Benchmarking Secure Vibe Coding of AI Agents via Reconstructing Vulnerability-Introducing Scenarios26 Sep 2025
- 2025"My productivity is boosted, but ..." Demystifying Users' Perception on AI Coding Assistants17 Aug 2025
- 2025Do Existing Testing Tools Really Uncover Gender Bias in Text-to-Image Models?27 Jan 2025
- 2024LEGION: Harnessing Pre-trained Language Models for GitHub Topic Recommendations with Distribution-Balance Loss9 Mar 2024
- 2023Multi-Granularity Detector for Vulnerability Fixes23 May 2023