CVE-2024-56138
notation-go's timestamp signature generation lacks certificate revocation check
Impact
This issue was identified during Quarkslab's audit of the timestamp feature. ### Summary During the timestamp signature generation, the revocation status of the certificate(s) used to generate the timestamp signature was not verified. ### Details 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`. ### Impact 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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| go | github.com/notaryproject/notation-go | >= 1.2.0-beta.1, <= 1.3.0-rc.1 | 1.3.0-rc.2 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/notaryproject/notation-go/commit/e7005a6d13e5ba472d4e166fbb085152f909e102
- https://github.com/notaryproject/notation-go/security/advisories/GHSA-45v3-38pc-874v
- https://github.com/advisories/GHSA-45v3-38pc-874v
- https://github.com/notaryproject/notation-go/commit/e99be1954a15673020150c5f8800b8174cd7428d
- https://nvd.nist.gov/vuln/detail/CVE-2024-56138
- https://pkg.go.dev/vuln/GO-2025-3381