CVE-2021-32660: TechDocs content sanitization bypass
First published: Thu Jun 03 2021(Updated: )
Backstage is an open platform for building developer portals, and techdocs-common contains common functionalities for Backstage's TechDocs. In versions of `@backstage/tehdocs-common` prior to 0.6.4, a malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data. The ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store. The vulnerability is patched in the `0.6.4` release of `@backstage/techdocs-common`.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Backstage Techdocs Common | <0.6.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-32660?
CVE-2021-32660 is considered a moderate severity vulnerability as it allows a malicious internal actor to upload harmful documentation content.
How do I fix CVE-2021-32660?
To remediate CVE-2021-32660, upgrade your @backstage/techdocs-common package to version 0.6.4 or later.
Who is affected by CVE-2021-32660?
CVE-2021-32660 affects users of @backstage/techdocs-common versions prior to 0.6.4, especially those allowing content uploads.
What are the potential impacts of CVE-2021-32660?
Exploiting CVE-2021-32660 can result in the injection of malicious scripts or content within the documentation, affecting users who access it.
Is there a way to mitigate the risks of CVE-2021-32660 before upgrading?
Users can implement access controls to limit who can upload documentation as a temporary measure until they upgrade to non-vulnerable versions.
- agent/weakness
- agent/softwarecombine
- agent/remedy
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/title
- agent/references
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/linuxfoundation
- canonical/backstage techdocs common