search

pomerium / ingress-controller

Pomerium Kubernetes Ingress Controller
https://pomerium.com
Apache License 2.0
22 stars 11 forks source link

build(deps): bump github.com/pomerium/pomerium from 0.26.1-0.20240701220939-e5e0b103016c to 0.26.1 #1001

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 3 months ago

Bumps github.com/pomerium/pomerium from 0.26.1-0.20240701220939-e5e0b103016c to 0.26.1.

Release notes

Sourced from github.com/pomerium/pomerium's releases.

v0.26.1

Security

Pomerium v0.26.1 includes multiple security updates:

  • The Pomerium user info page (at /.pomerium) unintentionally included serialized OAuth2 access and ID tokens from the logged-in user's session. These tokens are not intended to be exposed to end users, and have now been removed. CVE-2024-39315

    Credit to Vadim Sheydaev, aka Enr1g for reporting this issue.

  • This release also includes an update from Envoy 1.30.1 to Envoy 1.30.3 to address multiple security issues:

    • CVE-2024-34362: Crash (use-after-free) in EnvoyQuicServerStream
    • CVE-2024-34363: Crash due to uncaught nlohmann JSON exception
    • CVE-2024-34364: Envoy OOM vector from HTTP async client with unbounded response buffer for mirror response, and other components
    • CVE-2024-32974: Crash in EnvoyQuicServerStream::OnInitialHeadersComplete()
    • CVE-2024-32975: Crash in QuicheDataReader::PeekVarInt62Length()
    • CVE-2024-32976: Endless loop while decompressing Brotli data with extra input
    • CVE-2024-23326: Envoy incorrectly accepts HTTP 200 response for entering upgrade mode
    • CVE-2024-38525: datadog tracer does not handle trace headers with unicode characters

  • The release also removes a transitive dependency on the gopkg.in/square/go-jose.v2 library which is vulnerable to https://github.com/advisories/GHSA-c5q2-7r4c-mv6g.

What's Changed

Security

Fixes

Full Changelog: https://github.com/pomerium/pomerium/compare/v0.26.0...v0.26.1

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/pomerium/ingress-controller/network/alerts).
wasaga commented 2 months ago

we need main

dependabot[bot] commented 2 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.