Skip to content

chore(deps): update module github.com/sigstore/timestamp-authority to v2 [security] (alauda-v0.43.0) - autoclosed - #56

Closed
alaudaa-renovate[bot] wants to merge 1 commit into
alauda-v0.43.0from
renovate/alauda-v0.43.0-go-github.com-sigstore-timestamp-authority-vulnerability
Closed

chore(deps): update module github.com/sigstore/timestamp-authority to v2 [security] (alauda-v0.43.0) - autoclosed#56
alaudaa-renovate[bot] wants to merge 1 commit into
alauda-v0.43.0from
renovate/alauda-v0.43.0-go-github.com-sigstore-timestamp-authority-vulnerability

Conversation

@alaudaa-renovate

@alaudaa-renovate alaudaa-renovate Bot commented Jan 9, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
github.com/sigstore/timestamp-authority v1.2.9 -> v2.0.3 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2025-66564

Impact

Excessive memory allocation

Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string.

As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Patches

Upgrade to v2.0.3.

Workarounds

There are no workarounds with the service itself. If the service is behind a load balancer, configure the load balancer to reject excessively large requests.


Sigstore Timestamp Authority allocates excessive memory during request parsing

CVE-2025-66564 / GHSA-4qg8-fj49-pxjh / GO-2025-4192

More information

Details

Impact

Excessive memory allocation

Function api.ParseJSONRequest currently splits (via a call to strings.Split) an optionally-provided OID (which is untrusted data) on periods. Similarly, function api.getContentType splits the Content-Type header (which is also untrusted data) on an application string.

As a result, in the face of a malicious request with either an excessively long OID in the payload containing many period characters or a malformed Content-Type header, a call to api.ParseJSONRequest or api.getContentType incurs allocations of O(n) bytes (where n stands for the length of the function's argument). Relevant weakness: CWE-405: Asymmetric Resource Consumption (Amplification)

Patches

Upgrade to v2.0.3.

Workarounds

There are no workarounds with the service itself. If the service is behind a load balancer, configure the load balancer to reject excessively large requests.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sigstore/timestamp-authority (github.com/sigstore/timestamp-authority)

v2.0.3

Compare Source

Vulnerability Fixes

v2.0.2

Compare Source

This release bumps the Go version to 1.25.

v2.0.1

Compare Source

This release is identical to v2.0.0, as it only contains a fix for the release pipeline.

v2.0.0

Compare Source

v2.0.0 changes the default HTTP response code to 200 for timestamp responses,
which matches all other well-known TSA implementations. Sigstore clients already
handle both 200 and 201 response codes, so no changes are needed to clients.

If you need backwards compatibility, you can deploy the service with
--use-http-201.

This release also changes the format of the binary and container signature,
which is now a Sigstore bundle.
To verify a release, use the latest Cosign 3.x, verifying with
cosign verify-blob --bundle <artifact>-keyless.sigstore.json <artifact>.

Features

  • changes default HTTP response code to 200 for timestamp responses (#​1202)
  • feat: add configurable max request body size for TSA server (#​1176)

Testing

  • test: Add a K6 loadtest

Documentation

  • Minor improvements to documentation (#​1169)

Misc

  • (fix): minor gosec issues under x509.go (#​1201)

Configuration

📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@alaudaa-renovate

Copy link
Copy Markdown
Author

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 22 additional dependencies were updated

Details:

Package Change
github.com/go-openapi/analysis v0.23.0 -> v0.24.1
github.com/go-openapi/errors v0.22.2 -> v0.22.4
github.com/go-openapi/jsonpointer v0.21.0 -> v0.22.1
github.com/go-openapi/jsonreference v0.21.0 -> v0.21.3
github.com/go-openapi/loads v0.22.0 -> v0.23.2
github.com/go-openapi/runtime v0.28.0 -> v0.29.2
github.com/go-openapi/spec v0.21.0 -> v0.22.1
github.com/go-openapi/strfmt v0.23.0 -> v0.25.0
github.com/go-openapi/swag v0.24.1 -> v0.25.4
github.com/go-openapi/swag/cmdutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/conv v0.24.0 -> v0.25.4
github.com/go-openapi/swag/fileutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/jsonname v0.24.0 -> v0.25.4
github.com/go-openapi/swag/jsonutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/loading v0.24.0 -> v0.25.4
github.com/go-openapi/swag/mangling v0.24.0 -> v0.25.4
github.com/go-openapi/swag/netutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/stringutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/typeutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/yamlutils v0.24.0 -> v0.25.4
github.com/go-openapi/validate v0.24.0 -> v0.25.1
go.mongodb.org/mongo-driver v1.17.4 -> v1.17.6

@alaudaa-renovate alaudaa-renovate Bot changed the title chore(deps): update module github.com/sigstore/timestamp-authority to v2 [security] (alauda-v0.43.0) chore(deps): update module github.com/sigstore/timestamp-authority to v2 [security] (alauda-v0.43.0) - autoclosed Jan 15, 2026
@alaudaa-renovate alaudaa-renovate Bot closed this Jan 15, 2026
@alaudaa-renovate
alaudaa-renovate Bot deleted the renovate/alauda-v0.43.0-go-github.com-sigstore-timestamp-authority-vulnerability branch January 15, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant