Dagstuhl Research Online Publication Server· 2025
Detecting Functionality-Specific Vulnerabilities via Retrieving Individual Functionality-Equivalent APIs in Open-Source Repositories
- 16,189citations
- 2025year
Short summary
A new approach, APISS, effectively detects functionality-specific software vulnerabilities by retrieving equivalent APIs using API documentation and signatures, achieving 0.81 Top-1 Accuracy compared to baselines' 0.55.
AI-generated from the title and abstract; the full text is not read.
Key points
- APISS uses API doc strings and signatures, not code bodies, to find functionality-equivalent APIs for vulnerability detection.
- A Large Language Model enhances API embedding accuracy for retrieving equivalent APIs.
- APISS achieved 0.81 Top-1 Accuracy in retrieving equivalent APIs, significantly outperforming baselines (0.55).
- The method detected 179 new vulnerabilities and secured 60 CVE IDs, demonstrating practical security value.
AI-generated from the title and abstract; the full text is not read.
Abstract
Functionality-specific vulnerabilities, which mainly occur in Application Programming Interfaces (APIs) with specific functionalities, are crucial for software developers to detect and avoid. When detecting individual functionality-specific vulnerabilities, the existing two categories of approaches are ineffective because they consider only the API bodies and are unable to handle diverse implementations of functionality-equivalent APIs. To effectively detect functionality-specific vulnerabilities, we propose APISS, the first approach to utilize API doc strings and signatures instead of API bodies. APISS first retrieves functionality-equivalent APIs for APIs with existing vulnerabilities and then migrates Proof-of-Concepts (PoCs) of the existing vulnerabilities for newly detected vulnerable APIs. To retrieve functionality-equivalent APIs, we leverage a Large Language Model for API embedding to improve the accuracy and address the effectiveness and scalability issues suffered by the existing approaches. To migrate PoCs of the existing vulnerabilities for newly detected vulnerable APIs, we design a semi-automatic schema to substantially reduce manual costs. We conduct a comprehensive evaluation to empirically compare APISS with four state-of-the-art approaches of detecting vulnerabilities and two state-of-the-art approaches of retrieving functionality-equivalent APIs. The evaluation subjects include 180 widely used Java repositories using 10 existing vulnerabilities, along with their PoCs. The results show that APISS effectively retrieves functionality-equivalent APIs, achieving a Top-1 Accuracy of 0.81 while the best of the baselines under comparison achieves only 0.55. APISS is highly efficient: the manual costs are within 10 minutes per vulnerability and the end-to-end runtime overhead of testing one candidate API is less than 2 hours. APISS detects 179 new vulnerabilities and receives 60 new CVE IDs, bringing high value to security practice.
The authors' abstract, as published at the source. Dagstuhl Research Online Publication Server, 2025 · DOI ↗
Continue with a free account
Ask the paper: 3 free questions a day about this paper; save it, get its citation, new summaries every day for your field. Takeaways are Premium.
Continue free on the webSign in with Google or Apple; no card needed. You come back to this paper.
On your phone:
Field: Artificial Intelligence
Artificial IntelligenceComputer Science