This issue was identified during Quarkslab's audit of the timestamp feature.
During the timestamp signature generation, the revocation status of the certificate(s) used to generate the timestamp signature was not verified.
During timestamp signature generation, notation-go did not check the revocation status of the certificate chain used by the TSA. This oversight creates a vulnerability that could be exploited through a Man-in-The-Middle attack. An attacker could potentially use a compromised, intermediate, or revoked leaf certificate to generate a malicious countersignature, which would then be accepted and stored by notation.
This could lead to denial of service scenarios, particularly in CI/CD environments during signature verification processes because timestamp signature would fail due to the presence of a revoked certificate(s) potentially disrupting operations.
| Score | Percentile |
|---|---|
| 0.01% | 0.38% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 4.0 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-45v3-38pc-874v ↗ |
| CVE | CVE-2024-56138 ↗ |
| CWE id | Name |
|---|---|
| CWE-299 | Improper Check for Certificate Revocation |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| go | github.com/notaryproject/notation-go | >= 1.2.0-beta.1, <= 1.3.0-rc.1 | 1.3.0-rc.2 | — |