CVE-2024-53983

Backstage Scaffolder plugin vulnerable to Server-Side Request Forgery

Workarounds

Users can ensure that templates do not change git config.

References

If you have any questions or comments about this advisory:

Open an issue in the Backstage repository
Visit our Discord, linked to in Backstage README

A vulnerability is identified in Backstage Scaffolder template functionality where Server-Side Template Injection (SSTI) can be exploited to perform Git config injection. The vulnerability allows an attacker to capture privileged git tokens used by the Backstage Scaffolder plugin. With these tokens, unauthorized access to sensitive resources in git can be achieved. The impact is considered medium severity as the Backstage Threat Model recommends restricting access to adding and editing templates in the Backstage Catalog plugin.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2024-53983 has a CVSS score of 5.4 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.4.12, 0.5.1, 0.6.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue has been resolved in versions v0.4.12, v0.5.1 and v0.6.1 of the @backstage/plugin-scaffolder-node package. Users are encouraged to upgrade to this version to mitigate the vulnerability.

1. What is CVE-2024-53983? CVE-2024-53983 is a medium-severity server-side request forgery (SSRF) vulnerability in @backstage/plugin-scaffolder-node (npm), affecting versions < 0.4.12. It is fixed in 0.4.12, 0.5.1, 0.6.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2024-53983? CVE-2024-53983 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @backstage/plugin-scaffolder-node are affected by CVE-2024-53983? @backstage/plugin-scaffolder-node (npm) versions < 0.4.12 is affected.
4. Is there a fix for CVE-2024-53983? Yes. CVE-2024-53983 is fixed in 0.4.12, 0.5.1, 0.6.1. Upgrade to this version or later.
5. Is CVE-2024-53983 exploitable, and should I be worried? Whether CVE-2024-53983 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-53983 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-53983?
   • Upgrade @backstage/plugin-scaffolder-node to 0.4.12 or later
   • Upgrade @backstage/plugin-scaffolder-node to 0.5.1 or later
   • Upgrade @backstage/plugin-scaffolder-node to 0.6.1 or later

Other vulnerabilities in @backstage/plugin-scaffolder-node