{"answers":{"affected":"3 open source packages ship an affected version, including github.com/docker/distribution.","exploited":"There is no known exploitation of GHSA-qq97-vm5h-rrhg in the wild and no public exploit code.","fix":"Upgrade github.com/docker/distribution to a fixed version for your release line: 2.8.0 or 2.8.0+incompatible.","what":"GHSA-qq97-vm5h-rrhg is a vulnerability in github.com/docker/distribution, published on 8 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-qq97-vm5h-rrhg and fix it if it is affected.\n\nWhat it is: GHSA-qq97-vm5h-rrhg is a vulnerability in github.com/docker/distribution, published on 8 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-qq97-vm5h-rrhg in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/docker/distribution (Go): affected all versions; fixed in 2.8.0\n- github.com/docker/distribution (Go): affected all versions; fixed in 2.8.0\n- github.com/docker/distribution (Go): affected all versions; fixed in 2.8.0+incompatible\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-qq97-vm5h-rrhg/ (Markdown: https://insights.sbomify.com/GHSA-qq97-vm5h-rrhg/index.md)","id":"GHSA-qq97-vm5h-rrhg","markdown":"https://insights.sbomify.com/GHSA-qq97-vm5h-rrhg/index.md","name":"GHSA-qq97-vm5h-rrhg","record":{"aliases":["GO-2022-0379"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OCI Registry Client","requires_auth":"none","summary":"Attackers can bypass image attestation checks by exploiting OCI manifest type confusion via Content-Type headers, affecting registry clients relying on digest equivalence.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nSystems that rely on digest equivalence for image attestations may be vulnerable to type confusion.\n\n### Patches\n\nUpgrade to at least `v2.8.0-beta.1`  if you are running `v2.x` release. If you use the code from the `main` branch, update at least to the commit after [b59a6f827947f9e0e67df0cfb571046de4733586](https://github.com/distribution/distribution/commit/b59a6f827947f9e0e67df0cfb571046de4733586).\n\n### Workarounds\n\nThere is no way to work around this issue without patching.\n\n### References\n\nDue to [an oversight in the OCI Image Specification](https://github.com/opencontainers/image-spec/pull/411) that removed the embedded `mediaType` field from manifests, a maliciously crafted OCI Container Image can cause registry clients to parse the same image in two different ways without modifying the image’s digest by modifying the `Content-Type` header returned by a registry. This can invalidate a common pattern of relying on container image digests for equivalence.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [distribution](https://github.com/distribution/distribution) \n* Open an issue in [distribution-spec](https://github.com/opencontainers/distribution-spec) \n* Email us at [cncf-distribution-security@lists.cncf.io](mailto:cncf-distribution-security@lists.cncf.io)","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"OCI Manifest Type Confusion Issue","id":"GHSA-qq97-vm5h-rrhg","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2022"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["2.8.0"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/distribution","purl":null,"source":"GHSA-qq97-vm5h-rrhg"},{"ecosystem":"Go","fixed":["2.8.0"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/distribution","purl":"pkg:golang/github.com/docker/distribution","source":"GHSA-qq97-vm5h-rrhg"},{"ecosystem":"Go","fixed":["2.8.0+incompatible"],"introduced":["0"],"last_affected":[],"package":"github.com/docker/distribution","purl":"pkg:golang/github.com/docker/distribution","source":"GO-2022-0379"}],"products":null,"published":"2022-02-08","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass image attestation checks by exploiting OCI manifest type confusion via Content-Type headers, affecting registry clients relying on digest equivalence.","url":"https://insights.sbomify.com/GHSA-qq97-vm5h-rrhg/"}