# CVE-2023-6944: Rhdh: catalog-import function leaks credentials to frontend

> Attackers can view leaked GitLab access tokens in frontend error messages, enabling unauthorized repository access and code manipulation.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jan 2024
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-86rg-pf4c-5grg

## What is CVE-2023-6944?

CVE-2023-6944 is a medium-severity vulnerability in Linuxfoundation Backstage, published on 4 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in the Red Hat Developer Hub (RHDH). The catalog-import function leaks GitLab access tokens on the frontend when the base64 encoded GitLab token includes a newline at the end of the string. The sanitized error can display on the frontend, including the raw access token. Upon gaining access to this token and depending on permissions, an attacker could push malicious code to repositories, delete resources in Git, revoke or generate new keys, and sign code illegitimately.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

2 open source packages ship an affected version, including @backstage/backend-app-api. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@backstage/backend-app-api` | npm | All versions | 0.5.9-next.1 |
| `@backstage/backend-app-api` | npm | All versions | 0.5.9-next.1 |

Products: Linuxfoundation Backstage, Redhat Red Hat Developer Hub.

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

Upgrade @backstage/backend-app-api to 0.5.9-next.1 or later.

## Is CVE-2023-6944 being exploited?

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

## Other vulnerabilities in Linuxfoundation Backstage

- [CVE-2026-106501](https://insights.sbomify.com/CVE-2026-106501/): Backstage: Sensitive information exposure in Scaffolder (critical 9.6)
- [CVE-2026-106558](https://insights.sbomify.com/CVE-2026-106558/): Backstage: Improper validation of TechDocs MkDocs configuration (high 8.8)
- [CVE-2026-88064](https://insights.sbomify.com/CVE-2026-88064/): Backstage: Improper input validation in TechDocs MkDocs configuration (high 8.8)
- [CVE-2026-106459](https://insights.sbomify.com/CVE-2026-106459/): Backstage: Improper input validation in Sentry scaffolder actions (high 8.5)
- [CVE-2026-106486](https://insights.sbomify.com/CVE-2026-106486/): Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6944 is a medium-severity vulnerability in Linuxfoundation Backstage, published on 4 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-6944 in the wild and no public exploit code.

Affected packages and fixed versions:
- @backstage/backend-app-api (npm): affected all versions; fixed in 0.5.9-next.1
- @backstage/backend-app-api (npm): affected all versions; fixed in 0.5.9-next.1

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

## Sources

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

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