Git token theft via template-driven Git configuration
Published Nov 29, 2024 · Updated Dec 2, 2024
Server-side request forgery in Backstage Scaffolder Node before 0.4.12 and in 0.5.0 and 0.6.0 allows remote authenticated users to steal Git tokens. Scaffolder template evaluation accepts expressions that alter Git configuration, causing privileged Git authentication tokens to be disclosed during a template run. Exploitation requires permission to add or edit a Catalog template and interaction from a user who runs that malicious template.
Summary
What happened
Server-side request forgery in Backstage Scaffolder Node before 0.4.12 and in 0.5.0 and 0.6.0 allows remote authenticated users to steal Git tokens. Scaffolder template evaluation accepts expressions that alter Git configuration, causing privileged Git authentication tokens to be disclosed during a template run. Exploitation requires permission to add or edit a Catalog template and interaction from a user who runs that malicious template.
The record
- CVE
- CVE-2024-53983
- Published
- Nov 29, 2024
- Updated
- Dec 2, 2024
- Vendor
- Backstage
- Product
- Backstage
- Classifications
- CWE-918, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 29, 2024CVE publishedPublication date reported by the CVE source.
- Dec 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.4.12
- Affected versionversion== 0.5.0
- Affected versionversion== 0.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo