Security readout for executives and security teams
Plain-English summary
Bikeshed, a documentation/specification generator, could run operating system commands when processing an untrusted source file with special Inline Tag Command metadata. The risk is to developer workstations or build systems that generate HTML from attacker-influenced files, not ordinary website visitors.
Executive priority
Treat as a high-priority developer tooling issue where bikeshed is used in automated builds or contributor workflows. The main business risk is compromise of build hosts, exposed secrets, or tampered generated documentation if malicious input is processed.
Technical view
CVE-2021-23422 affects bikeshed before 3.0.0. Processing a malicious source file containing Inline Tag Command metadata can trigger arbitrary OS command execution, with command output embedded in generated HTML. CVSS 3.1 is 7.8 high: local attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in documentation, standards, or CI pipelines using bikeshed before 3.0.0 on untrusted or externally contributed source files. Public-facing applications are not directly implicated unless they invoke bikeshed on user-controlled input.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires someone or an automated build process to process a malicious bikeshed source file. That makes pull-request, documentation, and publishing workflows the most relevant threat context.
Researcher notes
The source bundle lists no CWE or CPE data. Key validation is whether Inline Tag Command metadata from untrusted files can reach a pre-3.0.0 bikeshed execution path. Avoid assuming network exposure or active exploitation without additional evidence.
Mitigation direction
- Upgrade bikeshed to version 3.0.0 or later.
- Do not process untrusted bikeshed source files with vulnerable versions.
- Review CI workflows that run bikeshed on external pull requests.
- Restrict build-system permissions and secrets available to documentation jobs.
- Check vendor and Snyk guidance for current remediation details.
Validation and detection
- Inventory projects and build images for bikeshed usage.
- Confirm dependency manifests or lockfiles do not reference bikeshed before 3.0.0.
- Review documentation pipelines for attacker-controlled source inputs.
- Verify CI jobs running bikeshed have minimal secrets and filesystem access.
- Retest documentation generation after upgrading bikeshed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-23422 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/tabatkins/bikeshed/commit/b2f668fca204260b1cad28d5078e93471cb6b2ddCVE reference · x_refsource_MISC
- https://snyk.io/vuln/SNYK-PYTHON-BIKESHED-1537646CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.