Headline
GHSA-p3v4-c93g-cmhw: BBOT's gitlab.py exposes globally configured "gitlab" API key
Summary
bbot’s gitlab.py sends the user’s “gitlab” API key to on-premise GitLab instances.
If a user has configured a gitlab.com API key using this mechanism, it may be leaked to an attacker-controlled server.
Impact
A user with a “gitlab” API key configured who uses bbot to scan a malicious webserver may leak their gitlab.com API key to an untrustworthy server.
Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.