Denial of Service (DoS) Affecting github.com/sigstore/cosign/cmd/cosign/cli/verify package, versions <1.12.0
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.Test your applications
- Snyk ID SNYK-GOLANG-GITHUBCOMSIGSTORECOSIGNCMDCOSIGNCLIVERIFY-3023732
- published 15 Sep 2022
- disclosed 15 Sep 2022
- credit codysoyland, asraa and haydentherapper
How to fix?
github.com/sigstore/cosign/cmd/cosign/cli/verify to version 1.12.0 or higher.
github.com/sigstore/cosign/cmd/cosign/cli/verify is a package that aims to make signatures invisible infrastructure.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to several vulnerabilities in
cosign verify-blob that will successfully verify an artifact when verification should have failed.
This vulnerability exists due to the following:
A cosign bundle can be crafted to successfully verify a blob even if the embedded
rekorBundledoes not reference the given signature.
When providing identity flags, the email and issuer of a certificate are not checked when verifying a Rekor bundle, and the GitHub Actions identity is never checked.
When providing an invalid
Rekorbundle, the experimental flag is successfully verified without any check.
When an invalid transparency log entry will result in immediate success for verification.
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm