# CVE-2021-3167: Information disclosure in n/a

> Administrators can view exposed JWT authentication tokens in virtual cluster server logs, potentially allowing unauthorized access.

- **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:** 15 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-22x7-r7fc-8grh

## What is CVE-2021-3167?

CVE-2021-3167 is a medium-severity vulnerability in n/a, published on 15 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Cloudera Data Engineering (CDE) 1.3.0, JWT authentication tokens are exposed to administrators in virtual cluster server logs.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2021-3167?

It affects 1 product.


Products: Cloudera Data Engineering.

## How do I fix CVE-2021-3167?

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

## Is CVE-2021-3167 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26936](https://insights.sbomify.com/CVE-2020-26936/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3167 and fix it if it is affected.

What it is: CVE-2021-3167 is a medium-severity vulnerability in n/a, published on 15 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-3167 in the wild and no public exploit code.

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

## Sources

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

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