# CVE-2023-22949: Information disclosure in n/a

> TigerGraph logs user credentials in base64, allowing administrators to harvest usernames and passwords from system logs.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-gx8h-h4pj-j52p

## What is CVE-2023-22949?

CVE-2023-22949 is a medium-severity vulnerability in n/a, published on 14 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in TigerGraph Enterprise Free Edition 3.x. There is logging of user credentials. All authenticated GSQL access requests are logged by TigerGraph in multiple places. Each request includes both the username and password of the user in an easily decodable base64 form. That could allow a TigerGraph administrator to effectively harvest usernames/passwords.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 2 products.


Products: Tigergraph Cloud, Tigergraph Tigergraph Enterprise.

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

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

## Is CVE-2023-22949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-22951](https://insights.sbomify.com/CVE-2023-22951/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22949 is a medium-severity vulnerability in n/a, published on 14 Apr 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-22949 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-2023-22949/ (Markdown: https://insights.sbomify.com/CVE-2023-22949/index.md)
```

## Sources

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

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