Bug found and resolved in Dependency Scanning
Feb 19, 2021Nicole Schwartz

Summary
This post details a bug in the Dependency Scanning analyzer (gemnasium) where the vulnerability database was not updating itself at scan time, affecting versions between v2.8.1 and v2.28.0. This resulted in outdated scan results. The fix involves updating to newer analyzer versions (gemnasium v2.28.1+, gemnasium-python v2.17.3+, gemnasium-maven v2.20.4+). Customers with custom registries or specific docker pull policies need to manually update their analyzer images.
More from the Bug Triage and Reporting trail
- Shai-Hulud copycat campaign targets Python developers through PyPI typosquatting
- Manage vulnerability noise at scale with auto-dismiss policies
- How to transform compliance observation management with GitLab
- Self-service security alert handling with GitLab's UAM
- How GitLab measures Red Team impact: The adoption rate metric