{"answers":{"affected":"2 open source packages ship an affected version, including @backstage/techdocs-common. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32660 in the wild and no public exploit code.","fix":"Upgrade @backstage/techdocs-common to 0.6.4 or later.","what":"CVE-2021-32660 is a medium-severity cross-site scripting vulnerability in backstage, published on 3 Jun 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-32660 and fix it if it is affected.\n\nWhat it is: CVE-2021-32660 is a medium-severity cross-site scripting vulnerability in backstage, published on 3 Jun 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-32660 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @backstage/techdocs-common (npm): affected all versions; fixed in 0.6.4\n- @backstage/techdocs-common (npm): affected all versions; fixed in 0.6.4\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-32660/ (Markdown: https://insights.sbomify.com/CVE-2021-32660/index.md)","id":"CVE-2021-32660","markdown":"https://insights.sbomify.com/CVE-2021-32660/index.md","name":"CVE-2021-32660","record":{"aliases":["GHSA-pwhf-39xg-4rxw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Backstage developer portal","requires_auth":"high_privilege","summary":"Attackers can bypass content sanitization in Backstage TechDocs to inject malicious scripts, potentially accessing sensitive data if hosted on the same origin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"\\@backstage\\/techdocs-common","vendor":"linuxfoundation"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"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`.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TechDocs content sanitization bypass","id":"CVE-2021-32660","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2021"},"n_packages":2,"n_references":3,"next":{"headline":"TechDocs object element script injection","id":"CVE-2021-32661"},"packages":[{"ecosystem":"npm","fixed":["0.6.4"],"introduced":["0"],"last_affected":[],"package":"@backstage/techdocs-common","purl":null,"source":"GHSA-pwhf-39xg-4rxw"},{"ecosystem":"npm","fixed":["0.6.4"],"introduced":["0"],"last_affected":[],"package":"@backstage/techdocs-common","purl":"pkg:npm/%40backstage/techdocs-common","source":"GHSA-pwhf-39xg-4rxw"}],"prev":{"headline":"Automatic room upgrade handling can be used maliciously to bridge a room non-consentually","id":"CVE-2021-32659"},"products":["backstage"],"published":"2021-06-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["backstage"]},"summary":"Attackers can bypass content sanitization in Backstage TechDocs to inject malicious scripts, potentially accessing sensitive data if hosted on the same origin.","url":"https://insights.sbomify.com/CVE-2021-32660/"}