Skip to content

Improperly Implemented path matching for in-toto-golang

Moderate severity GitHub Reviewed Published Sep 21, 2021 in in-toto/in-toto-golang • Updated Feb 1, 2023

Package

gomod github.com/in-toto/in-toto-golang (Go)

Affected versions

<= 0.2.0

Patched versions

0.3.0

Description

Impact

Authenticated attackers posing as functionaries (i.e., within a trusted set of users for a layout) are able to create attestations that may bypass DISALLOW rules in the same layout. An attacker with access to trusted private keys, may issue an attestation that contains a disallowed artifact by including path traversal semantics (e.g., foo vs dir/../foo).

Patches

The problem has been fixed in version 0.3.0.

Workarounds

Exploiting this vulnerability is dependent on the specific policy applied.

For more information

If you have any questions or comments about this advisory:

References

@adityasaky adityasaky published to in-toto/in-toto-golang Sep 21, 2021
Published by the National Vulnerability Database Sep 21, 2021
Reviewed Sep 21, 2021
Published to the GitHub Advisory Database Sep 22, 2021
Last updated Feb 1, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N

EPSS score

0.057%
(24th percentile)

Weaknesses

CVE ID

CVE-2021-41087

GHSA ID

GHSA-vrxp-mg9f-hwf3

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.