CVE-2023-33958: Notation's default `maxSignatureAttempts` in `notation verify` enables an endless data attack
6.5
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.21292%
CWE
Published
6/6/2023
Updated
11/5/2023
KEV Status
No
Technology
Go
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| github.com/notaryproject/notation | go | < 1.0.0-rc.6 | 1.0.0-rc.6 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from uncontrolled resource consumption (CWE-400) during signature verification. The advisory indicates the default maxSignatureAttempts parameter allowed endless processing of signatures from a compromised registry. The fix in v1.0.0-rc.6 likely introduced a limit check in the signature verification loop. The verifySignatures function (or equivalent) in the verification workflow would be responsible for iterating through signatures, and without a proper maxSignatureAttempts enforcement, it would cause resource exhaustion. This aligns with the vulnerability's impact description and the CWE classification.