# CVE-2022-32172: Zinc - Cross-Site Scripting

> An authenticated user can execute stored XSS via template names, potentially stealing credentials from other users.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7j6x-42mm-p7jm, GO-2023-1896

## What is CVE-2022-32172?

CVE-2022-32172 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.

### Official description

In Zinc, versions v0.1.9 through v0.3.1 are vulnerable to Stored Cross-Site Scripting when using the delete template functionality. When an authenticated user deletes a template with a XSS payload in the name field, the Javascript payload will be executed and allow an attacker to access the user’s credentials.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-32172?

5 open source packages ship an affected version, including github.com/zinclabs/zinc and github.com/zincsearch/zincsearch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zinclabs/zinc` | Go | From 0.1.9 | 0.3.2 |
| `github.com/zinclabs/zinc` | Go | From 0.1.9 | 0.3.2 |
| `github.com/zinclabs/zinc` | Go | From 0.1.9 | 0.3.2 |
| `github.com/zincsearch/zincsearch` | Go | From 0.1.9 | 0.3.2 |
| `github.com/zincsearch/zincsearch` | Go | From 0.1.9 | 0.3.2 |

Products: Zinclabs Zinc.

## How do I fix CVE-2022-32172?

Upgrade github.com/zinclabs/zinc to 0.3.2 or later.

## Is CVE-2022-32172 being exploited?

There is no known exploitation of CVE-2022-32172 in the wild and no public exploit code.

## Other vulnerabilities in zinc

- [CVE-2022-32171](https://insights.sbomify.com/CVE-2022-32171/): Zinc - Stored XSS (not scored)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32172 and fix it if it is affected.

What it is: CVE-2022-32172 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.
Exploitation: There is no known exploitation of CVE-2022-32172 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zinclabs/zinc (Go): affected from 0.1.9; fixed in 0.3.2
- github.com/zinclabs/zinc (Go): affected from 0.1.9; fixed in 0.3.2
- github.com/zinclabs/zinc (Go): affected from 0.1.9; fixed in 0.3.2
- github.com/zincsearch/zincsearch (Go): affected from 0.1.9; fixed in 0.3.2
- github.com/zincsearch/zincsearch (Go): affected from 0.1.9; fixed in 0.3.2

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-32172/ (Markdown: https://insights.sbomify.com/CVE-2022-32172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-32172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-32172
- OSV: https://osv.dev/vulnerability/CVE-2022-32172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-32172/
Summaries are generated and may contain mistakes; the official description above is the record.