Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Rust crate rustls to 0.23.0 [SECURITY] - autoclosed #7158

Closed
wants to merge 1 commit into from

Conversation

oxide-renovate[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
rustls workspace.dependencies minor 0.22.2 -> 0.23.0

GitHub Vulnerability Alerts

GHSA-qg5g-gv98-5ffh

A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use rustls::server::Acceptor::accept() are affected.

Servers that use tokio-rustls's LazyConfigAcceptor API are affected.

Servers that use tokio-rustls's TlsAcceptor API are not affected.

Servers that use rustls-ffi's rustls_acceptor_accept API are affected.


Configuration

📅 Schedule: Branch creation - "" in timezone America/Los_Angeles, Automerge - "after 8pm,before 6am" in timezone America/Los_Angeles.

🚦 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.

@oxide-renovate oxide-renovate bot added the dependencies Pull requests that update a dependency file label Nov 25, 2024
@oxide-renovate
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.23.18
    Updating crates.io index
error: failed to select a version for the requirement `rustls = "^0.22.4"`
candidate versions found which didn't match: 0.23.18
location searched: crates.io index
required by package `dropshot v0.13.0`
    ... which satisfies dependency `dropshot = "^0.13.0"` (locked to 0.13.0) of package `oximeter-instruments v0.1.0 (/tmp/renovate/repos/github/oxidecomputer/omicron/oximeter/instruments)`
    ... which satisfies path dependency `oximeter-instruments` (locked to 0.1.0) of package `omicron-gateway v0.1.0 (/tmp/renovate/repos/github/oxidecomputer/omicron/gateway)`
    ... which satisfies path dependency `omicron-gateway` (locked to 0.1.0) of package `gateway-test-utils v0.1.0 (/tmp/renovate/repos/github/oxidecomputer/omicron/gateway-test-utils)`
    ... which satisfies path dependency `gateway-test-utils` (locked to 0.1.0) of package `nexus-test-utils v0.1.0 (/tmp/renovate/repos/github/oxidecomputer/omicron/nexus/test-utils)`
    ... which satisfies path dependency `nexus-test-utils` (locked to 0.1.0) of package `omicron-cockroach-admin v0.1.0 (/tmp/renovate/repos/github/oxidecomputer/omicron/cockroach-admin)`

@oxide-renovate oxide-renovate bot changed the title Update Rust crate rustls to 0.23.0 [SECURITY] Update Rust crate rustls to 0.23.0 [SECURITY] - autoclosed Dec 13, 2024
@oxide-renovate oxide-renovate bot closed this Dec 13, 2024
@oxide-renovate oxide-renovate bot deleted the renovate/crate-rustls-vulnerability branch December 13, 2024 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants