{"answers":{"affected":"5 open source packages ship an affected version, including github.com/zinclabs/zinc and github.com/zincsearch/zincsearch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-32171 in the wild and no public exploit code.","fix":"Upgrade github.com/zinclabs/zinc to 0.3.2 or later.","what":"CVE-2022-32171 is a cross-site scripting vulnerability in zinc, published on 6 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-32171 and fix it if it is affected.\n\nWhat it is: CVE-2022-32171 is a cross-site scripting vulnerability in zinc, published on 6 Oct 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-32171 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/zinclabs/zinc (Go): affected from 0.1.9; fixed in 0.3.2\n- github.com/zinclabs/zinc (Go): affected from 0.1.9; fixed in 0.3.2\n- github.com/zinclabs/zinc (Go): affected from 0.1.9; fixed in 0.3.2\n- github.com/zincsearch/zincsearch (Go): affected from 0.1.9; fixed in 0.3.2\n- github.com/zincsearch/zincsearch (Go): affected from 0.1.9; fixed in 0.3.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-2022-32171/ (Markdown: https://insights.sbomify.com/CVE-2022-32171/index.md)","id":"CVE-2022-32171","markdown":"https://insights.sbomify.com/CVE-2022-32171/index.md","name":"CVE-2022-32171","record":{"aliases":["GHSA-4fgv-8448-gf82","GO-2023-1895"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Zinc search engine","requires_auth":"low_privilege","summary":"An authenticated user can trigger stored XSS via the delete user function, allowing attackers to steal credentials from other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Mend","cpe":[{"product":"zinc","vendor":"zinclabs"}],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In Zinc, versions v0.1.9 through v0.3.1 are vulnerable to Stored Cross-Site Scripting when using the delete user functionality. When an authenticated user deletes a user having a XSS payload in the user id field, the javascript payload will be executed and allow an attacker to access the user’s credentials.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Zinc - Stored XSS","id":"CVE-2022-32171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"xss","year":"2022"},"n_packages":5,"n_references":2,"next":{"headline":"Zinc - Cross-Site Scripting","id":"CVE-2022-32172"},"packages":[{"ecosystem":"Go","fixed":["0.3.2"],"introduced":["0.1.9"],"last_affected":[],"package":"github.com/zinclabs/zinc","purl":null,"source":"GHSA-4fgv-8448-gf82"},{"ecosystem":"Go","fixed":["0.3.2"],"introduced":["0.1.9"],"last_affected":[],"package":"github.com/zinclabs/zinc","purl":"pkg:golang/github.com/zinclabs/zinc","source":"GHSA-4fgv-8448-gf82"},{"ecosystem":"Go","fixed":["0.3.2"],"introduced":["0.1.9"],"last_affected":[],"package":"github.com/zinclabs/zinc","purl":"pkg:golang/github.com/zinclabs/zinc","source":"GO-2023-1895"},{"ecosystem":"Go","fixed":["0.3.2"],"introduced":["0.1.9"],"last_affected":[],"package":"github.com/zincsearch/zincsearch","purl":null,"source":"GHSA-4fgv-8448-gf82"},{"ecosystem":"Go","fixed":["0.3.2"],"introduced":["0.1.9"],"last_affected":[],"package":"github.com/zincsearch/zincsearch","purl":"pkg:golang/github.com/zincsearch/zincsearch","source":"GHSA-4fgv-8448-gf82"}],"prev":{"headline":"bytebase - Improper Authorization","id":"CVE-2022-32170"},"products":["zinc"],"published":"2022-10-06","related":[{"cvss_score":null,"headline":"Zinc - Cross-Site Scripting","id":"CVE-2022-32172","kev_date_added":null,"published":"2022-10-06"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["zinc"]},"summary":"An authenticated user can trigger stored XSS via the delete user function, allowing attackers to steal credentials from other users.","url":"https://insights.sbomify.com/CVE-2022-32171/"}