# CVE-2022-38599: Information disclosure in n/a

> An attacker can access the /user/get-role-list endpoint to leak role information, requiring an upgrade to Teleport.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 8 Dec 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vq4r-f49j-6ch9

## What is CVE-2022-38599?

CVE-2022-38599 is a medium-severity vulnerability in n/a, published on 8 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Teleport v3.2.2, Teleport v3.5.6-rc6, and Teleport v3.6.3-b2 was discovered to contain an information leak via the /user/get-role-list web interface.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Goteleport Teleport.

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

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

## Is CVE-2022-38599 being exploited?

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

Public exploit code:

- Teleport v3.2.2, Teleport v3.5.6-rc6, and Teleport v3.6.3-b2 was discovered to contain an information leak via the /user/get-role-list web interface. (github_poc): https://github.com/arleyna/CVE-2022-38599

## Other vulnerabilities in n/a

- [CVE-2021-41393](https://insights.sbomify.com/CVE-2021-41393/): Security feature bypass in n/a (critical 9.8)
- [CVE-2022-36633](https://insights.sbomify.com/CVE-2022-36633/): Improper token validation leading to code execution in Teleport (high 8.8)
- [CVE-2021-41395](https://insights.sbomify.com/CVE-2021-41395/): Other in n/a (medium 6.5)
- [CVE-2021-41394](https://insights.sbomify.com/CVE-2021-41394/): Supply chain in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38599 is a medium-severity vulnerability in n/a, published on 8 Dec 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-38599 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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