gittuf: Invalid intermediate policies trusted when the policy apply workflow is bypassed
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gittuf | gittuf | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
Upgrade to gittuf 0.17.0 or later, then run gittuf verify-ref over the full history of each protected reference. If an intermediate policy is invalid, verification stops with an error; review the reference state log and repository audit logs to find out whether a user with write access tampered with the policy.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In gittuf 0.4.0 through 0.16.0, when a policy update appears within the range of reference state log entries being verified, verification checks only the root of trust signatures of the new policy and not the signatures of its other metadata (rule files). A user trusted to push to the repository who bypasses gittuf policy apply and writes the policy reference and reference state log directly can make an invalid policy apply during verification, weakening or strengthening the rules for later changes. The update is still recorded in the reference state log. | |
| Title | gittuf: Invalid intermediate policies trusted when the policy apply workflow is bypassed | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|
No data.