# CVE-2022-32169: bytebase - Improper Authorization

> Low-privilege users can access admin issues via the /issue endpoint, allowing unauthorized viewing of sensitive administrative data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-5rc4-v5mj-g8c4

## What is CVE-2022-32169?

CVE-2022-32169 is a medium-severity missing authorization vulnerability in bytebase, published on 28 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The “Bytebase” application does not restrict low privilege user to access “admin issues“ for which an unauthorized user can view the “OPEN” and “CLOSED” issues by “Admin” and the affected endpoint is “/issue”.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-285 (Improper Authorization)

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

2 open source packages ship an affected version, including github.com/bytebase/bytebase. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bytebase/bytebase` | Go | From 0.1.0 to 1.0.4 | None |
| `github.com/bytebase/bytebase` | Go | From 0.1.0 to 1.0.4 | None |

Products: Bytebase Bytebase.

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

No fix has been published for CVE-2022-32169 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-32169 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32169 exists.

## Other vulnerabilities in bytebase

- [CVE-2022-32170](https://insights.sbomify.com/CVE-2022-32170/): bytebase - Improper Authorization (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32169 is a medium-severity missing authorization vulnerability in bytebase, published on 28 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32169 exists.

Affected packages and fixed versions:
- github.com/bytebase/bytebase (Go): affected from 0.1.0 up to 1.0.4; no fix listed
- github.com/bytebase/bytebase (Go): affected from 0.1.0 up to 1.0.4; no fix listed

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-32169/ (Markdown: https://insights.sbomify.com/CVE-2022-32169/index.md)
```

## Sources

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

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