@sigstore/oci npm Package Credential Exposure Issue: Early Warning
An early warning has been issued regarding a potential credential-exposure issue in the @sigstore/oci npm package, which could leak registry credentials to an attacker-controlled registry.
What happened
Reportedly, the @sigstore/oci npm package has a vulnerability where it can leak registry credentials to an attacker-controlled registry. This appears to occur due to a substring match in the registry selection process, potentially exposing credentials if the destination registry/image reference is influenced by an untrusted source and the attacker controls a registry whose hostname matches a substring of a configured Docker auth key.
The issue is under investigation and has been tracked with the ID GHSA-PF56-329R-95RW. It is recommended to upgrade to @sigstore/oci@0.7.1 or later to mitigate the credential-exposure issue. Affected components include @sigstore/oci (npm) versions prior to 0.7.1.
Professional software engineers are advised to review their dependencies and upgrade as necessary. For more detailed information, consult the primary sources linked in the summary.
How 0Day mitigates this
@sigstore/oci is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.