{"answers":{"affected":"3 open source packages ship an affected version, including zotregistry.dev/zot. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23208 exists.","fix":"Upgrade zotregistry.dev/zot to 2.1.2 or later.","what":"CVE-2025-23208 is a high-severity missing authorization vulnerability in project-zot zot, published on 17 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-23208 and fix it if it is affected.\n\nWhat it is: CVE-2025-23208 is a high-severity missing authorization vulnerability in project-zot zot, published on 17 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23208 exists.\n\nAffected packages and fixed versions:\n- zotregistry.dev/zot (Go): affected all versions; no fix listed\n- zotregistry.dev/zot (Go): affected all versions; fixed in 2.1.2\n- zotregistry.dev/zot (Go): affected all versions; fixed in 2.1.2\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/CVE-2025-23208/ (Markdown: https://insights.sbomify.com/CVE-2025-23208/index.md)","id":"CVE-2025-23208","markdown":"https://insights.sbomify.com/CVE-2025-23208/index.md","name":"CVE-2025-23208","record":{"aliases":["GHSA-c9p4-xwr9-rfhx","GO-2025-3409"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"OCI image registry","requires_auth":"none","summary":"Attackers retain revoked group access in zot registry due to append-only group storage, bypassing authorization controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zot","vendor":"zotregistry"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"zot is a production-ready vendor-neutral OCI image registry. The group data stored for users in the boltdb database (meta.db) is an append-list so group revocations/removals are ignored in the API. SetUserGroups is alled on login, but instead of replacing the group memberships, they are appended. This may be due to some conflict with the group definitions in the config file, but that wasn't obvious to me if it were the case. Any Zot configuration that relies on group-based authorization will not respect group remove/revocation by an IdP. This issue has been addressed in version 2.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"IdP group membership revocation ignored in zot","id":"CVE-2025-23208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Craft CMS Code Injection","id":"CVE-2025-23209"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot","purl":"pkg:golang/zotregistry.dev/zot","source":"GO-2025-3409"},{"ecosystem":"Go","fixed":["2.1.2"],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot","purl":null,"source":"GHSA-c9p4-xwr9-rfhx"},{"ecosystem":"Go","fixed":["2.1.2"],"introduced":["0"],"last_affected":[],"package":"zotregistry.dev/zot","purl":"pkg:golang/zotregistry.dev/zot","source":"GHSA-c9p4-xwr9-rfhx"}],"prev":{"headline":"\\htmlData does not validate attribute names in KaTeX","id":"CVE-2025-23207"},"products":["zot"],"published":"2025-01-17","related":[{"cvss_score":7.7,"headline":"zot create-only policy allows overwrite attempts of existing latest tag (update permission not required)","id":"CVE-2026-31801","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":4.3,"headline":"Cache driver GetBlob() allows read access to any blob without access control check","id":"CVE-2024-39897","kev_date_added":null,"published":"2024-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-22","vendors":["project-zot"]},"summary":"Attackers retain revoked group access in zot registry due to append-only group storage, bypassing authorization controls.","url":"https://insights.sbomify.com/CVE-2025-23208/"}