Vulnerable versions of Coverity Connect lack an error handler in the authentication logic for command line tooling that makes it vulnerable to an authentication bypass. A malicious actor with access to the /token API endpoint that either knows or guesses a valid username, can use this in a specially crafted HTTP request to bypass authentication. Successful exploitation allows the malicious actor to assume all roles and privileges granted to the valid user’s Coverity Connect account.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 4
https://community.blackduck.com/s/article/Black-Duck-Security-Advisory-CVE-2026…
disclosure@synopsys.com
https://community.blackduck.com/s/article/Instructions-on-how-to-block-token-en…
disclosure@synopsys.com
https://community.blackduck.com/s/article/WAF-IDS-IPS-Mitigation-Guidance
disclosure@synopsys.com
https://github.com/blackduck-inc/Coverity-Usage-Log-Analyzer
disclosure@synopsys.com