Security readout for executives and security teams
Plain-English summary
This flaw affects organizations using in-toto-golang for software supply chain integrity. A trusted participant with signing-key access could create an attestation that hides a disallowed artifact from policy checks. The issue is policy-dependent and fixed in version 0.3.0.
Executive priority
Treat this as a targeted supply chain integrity risk, not a broad internet-facing emergency. Prioritize teams using in-toto-golang in build or release workflows, especially where attestations gate deployment or compliance.
Technical view
in-toto-golang before 0.3.0 improperly matched artifact paths when enforcing DISALLOW rules. A trusted functionary could use path traversal semantics in an attestation so a disallowed artifact was treated as a different path. Impact is integrity-focused and depends on the layout policy.
Likely exposure
Exposure is likely limited to projects using in-toto-golang versions before 0.3.0, with layouts that rely on DISALLOW rules, and trusted functionaries or compromised keys able to submit attestations.
Exploitation context
The sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires low privileges inside the trusted layout set, access to trusted private keys, and a policy where path matching bypasses matter.
Researcher notes
The key condition is authenticated attestation creation by a trusted functionary. Focus analysis on path canonicalization during DISALLOW enforcement, layout policy dependence, and whether a build pipeline accepts attestations from affected library versions.
Mitigation direction
- Upgrade in-toto-golang to version 0.3.0 or later.
- Review vendor advisory and fix commit for implementation details.
- Audit layouts that depend on DISALLOW rules for supply chain controls.
- Rotate or investigate trusted functionary keys if misuse is suspected.
- Check vendor guidance before applying compensating controls.
Validation and detection
- Inventory applications and pipelines importing in-toto-golang.
- Confirm deployed dependency versions are 0.3.0 or later.
- Identify layouts using DISALLOW rules for artifact restrictions.
- Review attestations from trusted functionaries for suspicious path normalization differences.
- Verify key custody for functionaries allowed to produce attestations.
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.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-41087 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
- Medium
- CVSS
- 5.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N
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:H/PR:L/UI:N/S:C/C:N/I:H/A:N1.14Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.6MediumVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-vrxp-mg9f-hwf3CVE reference · x_refsource_CONFIRM
- https://github.com/in-toto/in-toto-golang/commit/f2c57d1e0f15e3ffbeac531829c696b72ecc4290CVE 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.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.