| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/notaryproject/notation-go | < 1.0.0-rc.3 | 1.0.0-rc.3 |
| notation-go | = 0.7.0= 0.8.0= 0.9.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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free