gittuf: Propagated controller policies not loaded during verification
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.18.0 or later, then run gittuf verify-ref over the full history of each protected reference. Policy propagation has been moved back into gittuf's developer mode.
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.10.0 through 0.17.0, the verification workflow does not load policy updates that are propagated from an upstream (controller) repository and recorded in the reference state log after the first entry being verified. Only the propagated policy in effect at the start of verification is applied, so later controller changes to global rules, such as threshold requirements and force-push blocks, are ignored and changes that these rules should block pass verification. | |
| Title | gittuf: Propagated controller policies not loaded during verification | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|