CVE-2024-56138Medium· 4.0▾ Sunlitnotation-go's timestamp signature generation lacks certificate revocation check
▾ Sunlit zone — Low / medium · no exploitation signal
impact 22 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.1%
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.
github.com/notaryproject/notation-go >= 1.2.0-beta.1, < 1.3.0-rc.2Upgrade to a patched release:
github.com/notaryproject/notation-go 1.3.0-rc.2Connected by shared product, vendor, weakness, or advisory.