# CVE-2023-22951: Hardcoded credentials in n/a

> Attackers can read a hardcoded authentication token from the configuration file to gain anonymous admin-level privileges on all REST API endpoints.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Apr 2023
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-cw85-fvjr-j5xv

## What is CVE-2023-22951?

CVE-2023-22951 is a high-severity vulnerability in n/a, published on 13 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in TigerGraph Enterprise Free Edition 3.x. It creates an authentication token for internal systems use. This token can be read from the configuration file. Using this token on the REST API provides an attacker with anonymous admin-level privileges on all REST API endpoints.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 2 products.


Products: Tigergraph Cloud, Tigergraph Tigergraph Enterprise.

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

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

## Is CVE-2023-22951 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-22949](https://insights.sbomify.com/CVE-2023-22949/): Information disclosure in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22951 is a high-severity vulnerability in n/a, published on 13 Apr 2023. 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-22951 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-22951/ (Markdown: https://insights.sbomify.com/CVE-2023-22951/index.md)
```

## Sources

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

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