# CVE-2023-32188: JWT token compromise can allow malicious actions including Remote Code Execution (RCE)

> Attackers can reverse engineer JWT tokens to forge valid credentials, enabling unauthorized access and remote code execution in NeuVector.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2024
- **Updated:** 16 Oct 2024
- **Also known as:** GHSA-622h-h2p8-743x

## What is CVE-2023-32188?

CVE-2023-32188 is a critical authentication bypass vulnerability in SUSE neuvector, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A user can reverse engineer the JWT token (JSON Web Token) used in authentication for Manager and API access, forging a valid NeuVector Token to perform malicious activity in NeuVector. This can lead to an RCE.

Weakness: CWE-1270 (Generation of Incorrect Security Tokens)

## Which versions are affected by CVE-2023-32188?

2 open source packages ship an affected version, including github.com/neuvector/neuvector.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/neuvector/neuvector` | Go | All versions | 0.0.0-20231003121714-be746957ee7c |
| `github.com/neuvector/neuvector` | Go | All versions | 0.0.0-20231003121714-be746957ee7c |

## How do I fix CVE-2023-32188?

Upgrade github.com/neuvector/neuvector to 0.0.0-20231003121714-be746957ee7c or later.

## Is CVE-2023-32188 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32188 and fix it if it is affected.

What it is: CVE-2023-32188 is a critical authentication bypass vulnerability in SUSE neuvector, published on 16 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32188 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/neuvector/neuvector (Go): affected all versions; fixed in 0.0.0-20231003121714-be746957ee7c
- github.com/neuvector/neuvector (Go): affected all versions; fixed in 0.0.0-20231003121714-be746957ee7c

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

## Sources

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

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