Skip to content

@backstage/backend-app-api leaks GitLab access tokens

High severity GitHub Reviewed Published Jan 4, 2024 to the GitHub Advisory Database • Updated Feb 5, 2024

Package

npm @backstage/backend-app-api (npm)

Affected versions

< 0.5.9-next.1

Patched versions

0.5.9-next.1

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.

References

Published by the National Vulnerability Database Jan 4, 2024
Published to the GitHub Advisory Database Jan 4, 2024
Reviewed Feb 5, 2024
Last updated Feb 5, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

EPSS score

0.049%
(20th percentile)

Weaknesses

CVE ID

CVE-2023-6944

GHSA ID

GHSA-86rg-pf4c-5grg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.