Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2022-29173 (High) detected in github.com/theupdateframework/go-tuf-v0.1.0 #119

Open
mend-bolt-for-github bot opened this issue Jun 15, 2022 · 2 comments
Labels
Mend: dependency security vulnerability Security vulnerability detected by WhiteSource no-issue-activity

Comments

@mend-bolt-for-github
Copy link
Contributor

mend-bolt-for-github bot commented Jun 15, 2022

CVE-2022-29173 - High Severity Vulnerability

Vulnerable Library - github.com/theupdateframework/go-tuf-v0.1.0

Go implementation of The Update Framework (TUF)

Library home page: https://proxy.golang.org/github.com/theupdateframework/go-tuf/@v/v0.1.0.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go.mod

Dependency Hierarchy:

  • github.com/sigstore/cosign-v1.0.1 (Root Library)
    • github.com/theupdateframework/go-tuf-v0.1.0 (Vulnerable Library)

Found in HEAD commit: df1f7d3f67826e841793324e4796be4fbd91c00f

Found in base branch: main

Vulnerability Details

go-tuf is a Go implementation of The Update Framework (TUF). go-tuf does not correctly implement the client workflow for updating the metadata files for roles other than the root role. Specifically, checks for rollback attacks are not implemented correctly meaning an attacker can cause clients to install software that is older than the software which the client previously knew to be available, and may include software with known vulnerabilities. In more detail, the client code of go-tuf has several issues in regards to preventing rollback attacks: 1. It does not take into account the content of any previously trusted metadata, if available, before proceeding with updating roles other than the root role (i.e., steps 5.4.3.1 and 5.5.5 of the detailed client workflow). This means that any form of version verification done on the newly-downloaded metadata is made using the default value of zero, which always passes. 2. For both timestamp and snapshot roles, go-tuf saves these metadata files as trusted before verifying if the version of the metafiles they refer to is correct (i.e., steps 5.5.4 and 5.6.4 of the detailed client workflow). A fix is available in version 0.3.0 or newer. No workarounds are known for this issue apart from upgrading.

Publish Date: 2022-05-05

URL: CVE-2022-29173

CVSS 3 Score Details (8.0)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: Required
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-66x3-6cw3-v5gj

Release Date: 2022-05-05

Fix Resolution: v0.3.0


Step up your Open Source Security Game with Mend here

@mend-bolt-for-github mend-bolt-for-github bot added the Mend: dependency security vulnerability Security vulnerability detected by WhiteSource label Jun 15, 2022
@github-actions
Copy link

Stale issue message

Copy link
Contributor Author

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mend: dependency security vulnerability Security vulnerability detected by WhiteSource no-issue-activity
Projects
None yet
Development

No branches or pull requests

0 participants