Distribution up to 3.0.0-rc.2 Certificate Chain authorization

Summaryinfo

A vulnerability labeled as problematic has been found in Distribution up to 3.0.0-rc.2. Impacted is an unknown function of the component Certificate Chain Handler. Such manipulation leads to authorization. This vulnerability is documented as CVE-2025-24976. The attack can be executed remotely. There is not any exploit available. Applying a patch is advised to resolve this issue.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Distribution up to 3.0.0-rc.2. Affected by this issue is an unknown part of the component Certificate Chain Handler. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is integrity. CVE summarizes:

Distribution is a toolkit to pack, ship, store, and deliver container content. Systems running registry versions 3.0.0-beta.1 through 3.0.0-rc.2 with token authentication enabled may be vulnerable to an issue in which token authentication allows an attacker to inject an untrusted signing key in a JSON web token (JWT). The issue lies in how the JSON web key (JWK) verification is performed. When a JWT contains a JWK header without a certificate chain, the code only checks if the KeyID (`kid`) matches one of the trusted keys, but doesn't verify that the actual key material matches. A fix for the issue is available at commit 5ea9aa028db65ca5665f6af2c20ecf9dc34e5fcd and expected to be a part of version 3.0.0-rc.3. There is no way to work around this issue without patching if the system requires token authentication.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-24976 since 01/29/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.

Applying the patch 5ea9aa028db65ca5665f6af2c20ecf9dc34e5fcd is able to eliminate this problem. The bugfix is ready for download at github.com.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• Distribution

Version

• 3.0.0-rc.0
• 3.0.0-rc.1
• 3.0.0-rc.2

License

• open-source

Website

• Product: https://github.com/distribution/distribution/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion