7.5 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
NONE
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
0.001 Low
EPSS
Percentile
38.0%
notation-go
users will find their application using excessive memory when verifying signatures and the application will be finally killed, and thus availability is impacted.
The problem has been patched in the release v1.0.0-rc.3. Users should upgrade their notation-go
packages to v1.0.0-rc.3
or above.
Users can review their own trust policy file and check if the identity string contains =#
. Meanwhile, users should only put trusted certificates in their trust stores referenced by their own trust policy files, and make sure the authenticity
validation is set to enforce
The notation-go
project would like to thank Adam Korczynski (@AdamKorcz) for responsibly disclosing this issue during a security fuzzing audit sponsored by CNCF and Shiwei Zhang (@shizhMSFT) for root cause analysis and detailed vulnerability report.
CPE | Name | Operator | Version |
---|---|---|---|
github.com/notaryproject/notation-go | lt | 1.0.0-rc.3 |