Reachability Analysis
Reachability analysis is a technique in software security used to determine whether a vulnerability is genuinely exploitable. By analyzing call chains, it determines whether a vulnerable function can be triggered by business code, thereby reducing false positives.
Timeline (last 90 days)
The core of reachability analysis is to determine whether a vulnerable function will actually be called by business code; if the call chain can be proven unreachable, the team can safely ignore that alert.
Reachability analysis can be seen as a refined extension of SCA, layering call chain analysis on top of version matching to narrow "a vulnerability exists" down to "the vulnerability can be triggered," thereby improving the signal-to-noise ratio of alerts.
In engineering practice, a hybrid approach combining static analysis and runtime instrumentation is typically used to build call graphs, and a certain number of false negatives and false positives is accepted.
Practical implications for development teams include: prioritizing reachable vulnerabilities and establishing traceable exemption records for unreachable alerts, incorporating the tools used by agents into software supply chain management, and configuring agent tools according to the principle of least privilege.
All Facts (4)
The core of reachability analysis is to determine whether a vulnerable function will actually be called by business code; if the call chain can be proven unreachable, the team can safely ignore that alert.
50%UnverifiedReachability analysis can be seen as a refined extension of SCA, layering call chain analysis on top of version matching to narrow "a vulnerability exists" down to "the vulnerability can be triggered," thereby improving the signal-to-noise ratio of alerts.
50%UnverifiedIn engineering practice, a hybrid approach combining static analysis and runtime instrumentation is typically used to build call graphs, and a certain number of false negatives and false positives is accepted.
50%UnverifiedPractical implications for development teams include: prioritizing reachable vulnerabilities and establishing traceable exemption records for unreachable alerts, incorporating the tools used by agents into software supply chain management, and configuring agent tools according to the principle of least privilege.
50%