Download of Code Without Integrity Check Affecting github.com/notaryproject/notation package, versions *


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.04% (9th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-GOLANG-GITHUBCOMNOTARYPROJECTNOTATION-6186554
  • published25 Jan 2024
  • disclosed19 Jan 2024
  • creditJustin Cappos

Introduced: 19 Jan 2024

CVE-2024-23332  (opens in a new tab)
CWE-494  (opens in a new tab)

How to fix?

There is no fixed version for github.com/notaryproject/notation.

Overview

Affected versions of this package are vulnerable to Download of Code Without Integrity Check due to the configuration with permissive trust policies. An external actor with control of a compromised container registry can provide outdated versions of OCI artifacts, such as Images, leading artifact consumers with relaxed trust policies to potentially use artifacts with signatures that are no longer valid. This could expose them to any exploits those artifacts may contain.

Notes:

  1. In Notary Project, an artifact publisher can control the validity period of artifact by specifying signature expiry during the signing process.

  2. Notary Project supports revocation to ensure the signature freshness. Artifact publishers can sign with short-lived certificates and revoke older certificates when necessary.

Workarounds

1)Using shorter signature validity periods along with processes to periodically resign artifacts, allows artifact producers to ensure that their consumers will only receive up-to-date artifacts.

2)Artifact consumers should correspondingly use a strict or equivalent trust policy that enforces signature expiry.

CVSS Base Scores

version 3.1