Commit b7809b8
authored
chore(deps): update module github.com/sigstore/timestamp-authority/v2 to v2.0.6 [security] (#2280)
This PR contains the following updates:
| Package | Type | Update | Change | OpenSSF |
|---|---|---|---|---|
|
[github.com/sigstore/timestamp-authority/v2](https://redirect.github.com/sigstore/timestamp-authority)
| indirect | patch | `v2.0.5` → `v2.0.6` | [](https://securityscorecards.dev/viewer/?uri=github.com/sigstore/timestamp-authority)
|
---
> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/331) for more information.
### GitHub Vulnerability Alerts
####
[CVE-2026-39984](https://redirect.github.com/sigstore/timestamp-authority/security/advisories/GHSA-xm5m-wgh2-rrg3)
### Authorization bypass via certificate bag manipulation in
sigstore/timestamp-authority verifier
An authorization bypass vulnerability exists in
sigstore/timestamp-authority verifier
(timestamp-authority/v2/pkg/verification): `VerifyTimestampResponse`
function correctly verifies the certificate chain but when the TSA
specific constraints are verified in `VerifyLeafCert`, the first non-CA
certificate from the PKCS#7 certificate bag is used instead of the leaf
certificate from the certificate chain. An attacker can exploit this by
prepending a forged certificate to the certificate bag while the message
is signed with an authorized key. The library validates the signature
using the one certificate but performs authorization checks on the
another, allowing an attacker to bypass some authorization controls.
This vulnerability does **not** apply to timestamp-authority service,
only to users of `timestamp-authority/v2/pkg/verification` package.
This vulnerability does **not** apply to sigstore-go even though it is a
user of `timestamp-authority/v2/pkg/verification`: Providing
`TSACertificate` option to `VerifyTimestampResponse` fully mitigates the
issue.
### Patches
The issue will be fixed in timestamp-authority 2.0.6
### Workarounds
Users of `VerifyTimestampResponse` can use the `TSACertificate` option
to specify the exact certificate they expect to be used: this fully
mitigates the issue.
### References
This issue was found after reading CVE-2026-33753 / GHSA-3xxc-pwj6-jgrj
(originally reported by @​Jaynornj and @​Pr00fOf3xpl0it)
---
### Release Notes
<details>
<summary>sigstore/timestamp-authority
(github.com/sigstore/timestamp-authority/v2)</summary>
###
[`v2.0.6`](https://redirect.github.com/sigstore/timestamp-authority/releases/tag/v2.0.6)
[Compare
Source](https://redirect.github.com/sigstore/timestamp-authority/compare/v2.0.5...v2.0.6)
#### What's Changed
- Ensure correct certificate is used for TSA auth checks
(GHSA-xm5m-wgh2-rrg3) by [@​jku](https://redirect.github.com/jku)
in
[#​1333](https://redirect.github.com/sigstore/timestamp-authority/pull/1333)
**Full Changelog**:
<sigstore/timestamp-authority@v2.0.5...v2.0.6>
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- ""
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR has been generated by [Renovate
Bot](https://redirect.github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMTMuMCIsInVwZGF0ZWRJblZlciI6IjQzLjExMy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Co-authored-by: ocmbot[bot] <125909804+ocmbot[bot]@users.noreply.github.com>1 parent 5c77b82 commit b7809b8
2 files changed
Lines changed: 19 additions & 19 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
270 | 270 | | |
271 | 271 | | |
272 | 272 | | |
273 | | - | |
| 273 | + | |
274 | 274 | | |
275 | 275 | | |
276 | 276 | | |
| |||
321 | 321 | | |
322 | 322 | | |
323 | 323 | | |
324 | | - | |
| 324 | + | |
325 | 325 | | |
326 | 326 | | |
327 | | - | |
| 327 | + | |
328 | 328 | | |
329 | 329 | | |
330 | 330 | | |
331 | | - | |
332 | | - | |
| 331 | + | |
| 332 | + | |
333 | 333 | | |
334 | 334 | | |
335 | 335 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
25 | | - | |
| 24 | + | |
| 25 | + | |
26 | 26 | | |
27 | 27 | | |
28 | 28 | | |
| |||
854 | 854 | | |
855 | 855 | | |
856 | 856 | | |
857 | | - | |
858 | | - | |
| 857 | + | |
| 858 | + | |
859 | 859 | | |
860 | 860 | | |
861 | 861 | | |
| |||
1036 | 1036 | | |
1037 | 1037 | | |
1038 | 1038 | | |
1039 | | - | |
1040 | | - | |
| 1039 | + | |
| 1040 | + | |
1041 | 1041 | | |
1042 | 1042 | | |
1043 | 1043 | | |
| |||
1067 | 1067 | | |
1068 | 1068 | | |
1069 | 1069 | | |
1070 | | - | |
1071 | | - | |
| 1070 | + | |
| 1071 | + | |
1072 | 1072 | | |
1073 | 1073 | | |
1074 | 1074 | | |
| |||
1109 | 1109 | | |
1110 | 1110 | | |
1111 | 1111 | | |
1112 | | - | |
1113 | | - | |
| 1112 | + | |
| 1113 | + | |
1114 | 1114 | | |
1115 | 1115 | | |
1116 | 1116 | | |
| |||
1172 | 1172 | | |
1173 | 1173 | | |
1174 | 1174 | | |
1175 | | - | |
1176 | | - | |
| 1175 | + | |
| 1176 | + | |
1177 | 1177 | | |
1178 | 1178 | | |
1179 | 1179 | | |
| |||
1185 | 1185 | | |
1186 | 1186 | | |
1187 | 1187 | | |
1188 | | - | |
1189 | | - | |
| 1188 | + | |
| 1189 | + | |
1190 | 1190 | | |
1191 | 1191 | | |
1192 | 1192 | | |
| |||
0 commit comments