gittuf: File protection rules bypassed for filenames with special characters
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.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gittuf | Gittuf |
|
Vendor Solution
Upgrade to gittuf 0.18.0 or later, which asks Git for raw paths. Then re-run verification (gittuf verify-ref) for each protected reference: a reference that passed verification before the upgrade but fails after it contains a change that should have been blocked.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.098% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gittuf
Gittuf gittuf |
|
| Vendors & Products |
Gittuf
Gittuf gittuf |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In gittuf before 0.18.0, verification of file protection rules uses the quoted, escaped pathnames that Git prints by default for files with special characters (for example non-ASCII characters) instead of the raw paths. Such paths do not match patterns like file:internal/*, so the files are treated as unprotected, and a user who is not authorized by a file protection rule can change a protected file whose name contains special characters and still pass verification. | |
| Title | gittuf: File protection rules bypassed for filenames with special characters | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|