CVE-2024-22189
QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
CVE-2024-22189- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
EUVDEUVD-2024-1180
7.5
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
EUVD-2024-1180- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-c33x-xqrf-c478
7.5
QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.
I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/. I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683
There's no way to mitigate this attack, please update quic-go to a version that contains the fix.
- Record
GHSA-c33x-xqrf-c478- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-400, CWE-770
- Updated
- 2026-11-02
NVD
7.5
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
CVE-2024-22189- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
OSVALPINE-CVE-2024-22189
7.5
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
ALPINE-CVE-2024-22189- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-03
OSV
7.5
QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
CVE-2024-22189- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-770
- Updated
- 2026-11-02
Show 16 moreShow less
OSVDEBIAN-CVE-2024-22189
7.5
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
DEBIAN-CVE-2024-22189- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVGHSA-c33x-xqrf-c478
7.5
QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.
I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/. I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683
There's no way to mitigate this attack, please update quic-go to a version that contains the fix.
- Record
GHSA-c33x-xqrf-c478- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-400, CWE-770
- Updated
- 2026-11-02
OSVRHSA-2024:8534
7.5
Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Release Update
- Record
RHSA-2024:8534- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2024-22189
7.5
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
UBUNTU-CVE-2024-22189- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVAZL-39749 No score
CVE-2024-22189 affecting package coredns for versions less than 1.11.1-2
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
AZL-39749- Updated
- 2026-11-02
OSVAZL-39851 No score
CVE-2024-22189 affecting package coredns for versions less than 1.11.1-6
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Record
AZL-39851- Updated
- 2026-11-02
OSVGO-2024-2682 No score
Denial of service via connection starvation in github.com/quic-go/quic-go
An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.
- Record
GO-2024-2682- Updated
- 2026-11-02
OSVopenSUSE-RU-2026:21160-1 No score
Recommended update for dnscrypt-proxy
This update for dnscrypt-proxy fixes the following issues:
Changes in dnscrypt-proxy:
-
Update to version 2.1.16
- The "tls_cipher_suite" option is now a no-op. Modern TLS stacks no longer expose cipher suite selection in a meaningful way, and the option had become misleading
- A log size of 0 no longer means "unlimited"; it now correctly disables rotation by size
- A new "tls_prefer_rsa" option has been added to prefer RSA cipher suites during the TLS handshake, useful on systems without hardware AES
- The IP allow/block plugins now support CIDR ranges in addition to single addresses and prefix matching
- Forwarding rules now support
$RESOLVCONF:<file>to pick up upstream resolvers from a resolv.conf-style file, complementing the existing$DHCPsyntax - Servers that hit a transient high RTT could previously stay penalized forever and never come back into rotation; their RTT estimate now decays so they can recover
- Servers are no longer penalized for slow responses when the response is actually being served from the stale cache
- The HTTP transport now handles
Alt-Svc: clearproperly and reuses HTTP connections more aggressively - The cache TTL is now an explicit, configurable parameter rather than being derived implicitly
- The ""-resolve"" command now reports incomplete DNSSEC support instead of silently treating partial signatures as a success
- "jsdelivr is now offered as an alternative source URL for resolver lists, providing more redundancy when the primary mirrors are unreachable
-
boo#1260280: vendored google.golang.org/grpc v1.80.0
-
boo#1265785: vendored golang.org/x/net v0.54.0
-
Update to version 2.1.15
- Proxy hostnames (when using SOCKS/HTTP proxies) are now pre-resolved using bootstrap resolvers if they are domain names
- Dynamically reduces timeouts as the connection limit is approached
- Fixed double-bracketing of IPv6 addresses in DoH stamps
- Cache statistics are now more accurate by only counting queries that actually participate in caching
- Multiple IP addresses per hostname are now cached instead of randomly selecting one
-
Update to version 2.1.14
- Added support for client IP address encryption in logs
-
Update to version 2.1.13
- Manual configuration reload via SIGHUP is now supported regardless of the hot-reload setting, providing more flexibility for system administrators
- Fixed a regression in IP prefix matching for allow/block lists that could cause incorrect filtering behavior
- the generate-domains-blocklist script now handles poor network conditions more gracefully
-
Update to version 2.1.12
- weighted Power of Two (WP2) load balancing strategy has been implemented as the default
- optional Prometheus metrics endpoint has been added for monitoring
- additional records in queries are now properly removed before forwarding
- simple view UI has been removed
-
Update to version 2.1.11
- web-based monitoring user interface added
- configuration files hot-reloading implemented
- HTTP/3 probing
- added parallel downloading of block lists
-
Updated to version 2.1.8
- Dependencies have been updated, notably the QUIC implementation, which could be vulnerable to denial-of-service attacks.
- In forwarding rules, the target can now optionally include a non-standard DNS port number. The port number is also now optional when using IPv6.
- An annoying log message related to permissions on Windows has been suppressed.
- Resolver IP addresses can now be refreshed more frequently. Additionally, jitter has been introduced to prevent all resolvers from being refreshed simultaneously. Further changes have been implemented to mitigate issues arising from multiple concurrent attempts to resolve a resolver's IP address.
- An empty value for "tls_cipher_suite" is now equivalent to leaving the property undefined.…
- Record
openSUSE-RU-2026:21160-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:0211-1 No score
Security update for caddy
This update for caddy fixes the following issues:
Update to version 2.8.4:
- cmd: fix regression in auto-detect of Caddyfile (#6362)
- Tag v2.8.3 was mistakenly made on the v2.8.2 commit and is skipped
Update to version 2.8.2:
- cmd: fix auto-detetction of .caddyfile extension (#6356)
- caddyhttp: properly sanitize requests for root path (#6360)
- caddytls: Implement certmagic.RenewalInfoGetter
Update to version 2.8.1:
- caddyhttp: Fix merging consecutive
client_iporremote_ipmatchers (#6350) - core: MkdirAll appDataDir in InstanceID with 0o700 (#6340)
Update to version 2.8.0:
- acmeserver: Add
sign_with_rootfor Caddyfile (#6345) - caddyfile: Reject global request matchers earlier (#6339)
- core: Fix bug in AppIfConfigured (fix #6336)
- fix a typo (#6333)
- autohttps: Move log WARN to INFO, reduce confusion (#6185)
- reverseproxy: Support HTTP/3 transport to backend (#6312)
- context: AppIfConfigured returns error; consider not-yet-provisioned modules (#6292)
- Fix lint error about deprecated method in smallstep/certificates/authority
- go.mod: Upgrade dependencies
- caddytls: fix permission requirement with AutomationPolicy (#6328)
- caddytls: remove ClientHelloSNICtxKey (#6326)
- caddyhttp: Trace individual middleware handlers (#6313)
- templates: Add
pathEscapetemplate function and use it in file browser (#6278) - caddytls: set server name in context (#6324)
- chore: downgrade minimum Go version in go.mod (#6318)
- caddytest: normalize the JSON config (#6316)
- caddyhttp: New experimental handler for intercepting responses (#6232)
- httpcaddyfile: Set challenge ports when http_port or https_port are used
- logging: Add support for additional logger filters other than hostname (#6082)
- caddyhttp: Log 4xx as INFO; 5xx as ERROR (close #6106)
- caddyhttp: Alter log message when request is unhandled (close #5182)
- reverseproxy: Pointer to struct when loading modules; remove LazyCertPool (#6307)
- tracing: add trace_id var (
http.vars.trace_idplaceholder) (#6308) - go.mod: CertMagic v0.21.0
- reverseproxy: Implement health_follow_redirects (#6302)
- caddypki: Allow use of root CA without a key. Fixes #6290 (#6298)
- go.mod: Upgrade to quic-go v0.43.1
- reverseproxy: HTTP transport: fix PROXY protocol initialization (#6301)
- caddytls: Ability to drop connections (close #6294)
- httpcaddyfile: Fix expression matcher shortcut in snippets (#6288)
- caddytls: Evict internal certs from cache based on issuer (#6266)
- chore: add warn logs when using deprecated fields (#6276)
- caddyhttp: Fix linter warning about deprecation
- go.mod: Upgrade to quic-go v0.43.0
- fileserver: Set 'Vary: Accept-Encoding' header (see #5849)
- events: Add debug log
- reverseproxy: handle buffered data during hijack (#6274)
- ci: remove
androidandplan9from cross-build workflow (#6268) - run
golangci-lint run --fix --fast(#6270) - caddytls: Option to configure certificate lifetime (#6253)
- replacer: Implement
file.*global replacements (#5463) - caddyhttp: Address some Go 1.20 features (#6252)
- Quell linter (false positive)
- reverse_proxy: Add grace_period for SRV upstreams to Caddyfile (#6264)
- doc: add
verifierinClientAuthenticationcaddyfile marshaler doc (#6263) - caddytls: Add Caddyfile support for on-demand permission module (close #6260)
- reverseproxy: Remove long-deprecated buffering properties
- reverseproxy: Reuse buffered request body even if partially drained
- reverseproxy: Accept EOF when buffering
- logging: Fix default access logger (#6251)
- fileserver: Improve Vary handling (#5849)
- cmd: Only validate config is proper JSON if config slice has data (#6250)
- staticresp: Use the evaluated response body for sniffing JSON content-type (#6249)
- encode: Slight fix for the previous commit
- encode: Improve Etag handling (fix #5849)
- httpcaddyfile: Skip automate loader if…
- Record
openSUSE-SU-2024:0211-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:0220-1 No score
Security update for caddy
This update for caddy fixes the following issues:
-
Update to version 2.8.4:
- cmd: fix regression in auto-detect of Caddyfile (#6362)
- Tag v2.8.3 was mistakenly made on the v2.8.2 commit and is skipped
-
Update to version 2.8.2:
- cmd: fix auto-detetction of .caddyfile extension (#6356)
- caddyhttp: properly sanitize requests for root path (#6360)
- caddytls: Implement certmagic.RenewalInfoGetter
- build(deps): bump golangci/golangci-lint-action from 5 to 6 (#6361)
-
Update to version 2.8.1:
- caddyhttp: Fix merging consecutive
client_iporremote_ipmatchers (#6350) - core: MkdirAll appDataDir in InstanceID with 0o700 (#6340)
- caddyhttp: Fix merging consecutive
-
Update to version 2.8.0:
- acmeserver: Add
sign_with_rootfor Caddyfile (#6345) - caddyfile: Reject global request matchers earlier (#6339)
- core: Fix bug in AppIfConfigured (fix #6336)
- fix a typo (#6333)
- autohttps: Move log WARN to INFO, reduce confusion (#6185)
- reverseproxy: Support HTTP/3 transport to backend (#6312)
- context: AppIfConfigured returns error; consider not-yet-provisioned modules (#6292)
- Fix lint error about deprecated method in smallstep/certificates/authority
- go.mod: Upgrade dependencies
- caddytls: fix permission requirement with AutomationPolicy (#6328)
- caddytls: remove ClientHelloSNICtxKey (#6326)
- caddyhttp: Trace individual middleware handlers (#6313)
- templates: Add
pathEscapetemplate function and use it in file browser (#6278) - caddytls: set server name in context (#6324)
- chore: downgrade minimum Go version in go.mod (#6318)
- caddytest: normalize the JSON config (#6316)
- caddyhttp: New experimental handler for intercepting responses (#6232)
- httpcaddyfile: Set challenge ports when http_port or https_port are used
- logging: Add support for additional logger filters other than hostname (#6082)
- caddyhttp: Log 4xx as INFO; 5xx as ERROR (close #6106)
- Second half of 6dce493
- caddyhttp: Alter log message when request is unhandled (close #5182)
- chore: Bump Go version in CI (#6310)
- go.mod: go 1.22.3
- Fix typos (#6311)
- reverseproxy: Pointer to struct when loading modules; remove LazyCertPool (#6307)
- tracing: add trace_id var (
http.vars.trace_idplaceholder) (#6308) - go.mod: CertMagic v0.21.0
- reverseproxy: Implement health_follow_redirects (#6302)
- caddypki: Allow use of root CA without a key. Fixes #6290 (#6298)
- go.mod: Upgrade to quic-go v0.43.1
- reverseproxy: HTTP transport: fix PROXY protocol initialization (#6301)
- caddytls: Ability to drop connections (close #6294)
- build(deps): bump golangci/golangci-lint-action from 4 to 5 (#6289)
- httpcaddyfile: Fix expression matcher shortcut in snippets (#6288)
- caddytls: Evict internal certs from cache based on issuer (#6266)
- chore: add warn logs when using deprecated fields (#6276)
- caddyhttp: Fix linter warning about deprecation
- go.mod: Upgrade to quic-go v0.43.0
- fileserver: Set 'Vary: Accept-Encoding' header (see #5849)
- events: Add debug log
- reverseproxy: handle buffered data during hijack (#6274)
- ci: remove
androidandplan9from cross-build workflow (#6268) - run
golangci-lint run --fix --fast(#6270) - caddytls: Option to configure certificate lifetime (#6253)
- replacer: Implement
file.*global replacements (#5463) - caddyhttp: Address some Go 1.20 features (#6252)
- Quell linter (false positive)
- reverse_proxy: Add grace_period for SRV upstreams to Caddyfile (#6264)
- doc: add
verifierinClientAuthenticationcaddyfile marshaler doc (#6263) - caddytls: Add Caddyfile support for on-demand permission module (close #6260)
- reverseproxy: Remove long-deprecated buffering properties
- reverseproxy: Reuse buffered request body even if partially drained
- reverseproxy: Accept EOF when buffering
- logging: Fix default access logger (#6251)
- fileserver: Improve Vary handling (#5849)
- cmd: Only validate config is proper…
- acmeserver: Add
- Record
openSUSE-SU-2024:0220-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:0319-1 No score
Security update for coredns
This update for coredns fixes the following issues:
Update to version 1.11.3:
- optimize the performance for high qps (#6767)
- bump deps
- Fix zone parser error handling (#6680)
- Add alternate option to forward plugin (#6681)
- fix: plugin/file: return error when parsing the file fails (#6699)
- [fix:documentation] Clarify autopath README (#6750)
- Fix outdated test (#6747)
- Bump go version from 1.21.8 to 1.21.11 (#6755)
- Generate zplugin.go correctly with third-party plugins (#6692)
- dnstap: uses pointer receiver for small response writer (#6644)
- chore: fix function name in comment (#6608)
- [plugin/forward] Strip local zone from IPV6 nameservers (#6635)
- fixes CVE-2023-30464
- fixes CVE-2023-28452
Update to upstream head (git commit #5a52707):
- bump deps to address security issue CVE-2024-22189
- Return RcodeServerFailure when DNS64 has no next plugin (#6590)
- add plusserver to adopters (#6565)
- Change the log flags to be a variable that can be set prior to calling Run (#6546)
- Enable Prometheus native histograms (#6524)
- forward: respect context (#6483)
- add client labels to k8s plugin metadata (#6475)
- fix broken link in webpage (#6488)
- Repo controlled Go version (#6526)
- removed the mutex locks with atomic bool (#6525)
Update to version 1.11.2:
- rewrite: fix multi request concurrency issue in cname rewrite (#6407)
- plugin/tls: respect the path specified by root plugin (#6138)
- plugin/auto: warn when auto is unable to read elements of the directory tree (#6333)
- fix: make the codeowners link relative (#6397)
- plugin/etcd: the etcd client adds the DialKeepAliveTime parameter (#6351)
- plugin/cache: key cache on Checking Disabled (CD) bit (#6354)
- Use the correct root domain name in the proxy plugin's TestHealthX tests (#6395)
- Add PITS Global Data Recovery Services as an adopter (#6304)
- Handle UDP responses that overflow with TC bit with test case (#6277)
- plugin/rewrite: add rcode as a rewrite option (#6204)
-
CVE-2024-0874: coredns: CD bit response is cached and served later
-
Update to version 1.11.1:
- Revert “plugin/forward: Continue waiting after receiving malformed responses
- plugin/dnstap: add support for “extra” field in payload
- plugin/cache: fix keepttl parsing
-
Update to version 1.11.0:
- Adds support for accepting DNS connections over QUIC (doq).
- Adds CNAME target rewrites to the rewrite plugin.
- Plus many bug fixes, and some security improvements.
- This release introduces the following backward incompatible changes:
- In the kubernetes plugin, we have dropped support for watching Endpoint and Endpointslice v1beta, since all supported K8s versions now use Endpointslice.
- The bufsize plugin changed its default size limit value to 1232
- Some changes to forward plugin metrics.
-
Update to version 1.10.1:
- Corrected architecture labels in multi-arch image manifest
- A new plugin timeouts that allows configuration of server listener timeout durations
- acl can drop queries as an action
- template supports creating responses with extended DNS errors
- New weighted policy in loadbalance
- Option to serve original record TTLs from cache
-
Update to version 1.10.0:
- core: add log listeners for k8s_event plugin (#5451)
- core: log DoH HTTP server error logs in CoreDNS format (#5457)
- core: warn when domain names are not in RFC1035 preferred syntax (#5414)
- plugin/acl: add support for extended DNS errors (#5532)
- plugin/bufsize: do not expand query UDP buffer size if already set to a smaller value (#5602)
- plugin/cache: add cache disable option (#5540)
- plugin/cache: add metadata for wildcard record responses (#5308)
- plugin/cache: add option to adjust SERVFAIL response cache TTL (#5320)
- plugin/cache: correct responses to Authenticated Data requests (#5191)
- plugin/dnstap: add identity and version support for the dnstap plugin (#5555) *…
- Record
openSUSE-SU-2024:0319-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:13845-1 No score
kubo-0.27.0-2.1 on GA media
These are all security issues fixed in the kubo-0.27.0-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:13845-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:13847-1 No score
syncthing-1.27.6-1.1 on GA media
These are all security issues fixed in the syncthing-1.27.6-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:13847-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:13849-1 No score
coredns-1.11.1-5.1 on GA media
These are all security issues fixed in the coredns-1.11.1-5.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:13849-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:13865-1 No score
golang-github-v2fly-v2ray-core-5.15.1-1.1 on GA media
These are all security issues fixed in the golang-github-v2fly-v2ray-core-5.15.1-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:13865-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:14014-1 No score
caddy-2.8.4-1.1 on GA media
These are all security issues fixed in the caddy-2.8.4-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:14014-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/quic-go/quic-goGo |
before 0.42.0 | 0.42.0 |
kuboAlpine:v3.20 |
before 0.28.0-r0 | 0.28.0-r0 |
kuboAlpine:v3.21 |
before 0.28.0-r0 | 0.28.0-r0 |
kuboAlpine:v3.22 |
before 0.28.0-r0 | 0.28.0-r0 |
kuboAlpine:v3.23 |
before 0.28.0-r0 | 0.28.0-r0 |
kuboAlpine:v3.24 |
before 0.28.0-r0 | 0.28.0-r0 |
corednsAzure Linux:3 |
before 1.11.1-2 | 1.11.1-2 |
corednsAzure Linux:2 |
before 1.11.1-6 | 1.11.1-6 |
golang-github-lucas-clemente-quic-goDebian:12 |
All versions, plus listed versions 0.29.0-10.29.2-10.29.2-20.29.2-30.37.0-1 Show 19 moreShow less0.37.4-10.37.4-1~bpo12+10.38.2-10.38.2-20.46.0-10.46.0-20.46.0-2~bpo12+10.50.0-10.50.1-10.50.1-20.54.0-10.54.0-20.54.0-30.54.1-10.55.0-10.59.0-10.59.0-20.59.0-2~bpo13+10.64.1-1 |
None known |
golang-github-lucas-clemente-quic-goDebian:13 |
before 0.46.0-1 | 0.46.0-1 |
Show 33 moreShow less
| Package | Affected | Fixed |
|---|---|---|
golang-github-lucas-clemente-quic-goDebian:14 |
before 0.46.0-1 | 0.46.0-1 |
automation-gateway-serverRed Hat:ansible_automation_platform:2.5::el8 From an advisory covering 4 CVEs |
before 0:2.5.3-1.el8ap | 0:2.5.3-1.el8ap |
automation-gateway-serverRed Hat:ansible_automation_platform:2.5::el9 From an advisory covering 4 CVEs |
before 0:2.5.3-1.el9ap | 0:2.5.3-1.el9ap |
receptorRed Hat:ansible_automation_platform_developer:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptorctlRed Hat:ansible_automation_platform_developer:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptorRed Hat:ansible_automation_platform_inside:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptorctlRed Hat:ansible_automation_platform_inside:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptorRed Hat:ansible_automation_platform:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptor-debuginfoRed Hat:ansible_automation_platform:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptor-debugsourceRed Hat:ansible_automation_platform:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptorctlRed Hat:ansible_automation_platform:2.5::el8 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el8ap | 0:1.4.9-2.el8ap |
receptorRed Hat:ansible_automation_platform_developer:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptorctlRed Hat:ansible_automation_platform_developer:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptorRed Hat:ansible_automation_platform_inside:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptorctlRed Hat:ansible_automation_platform_inside:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptorRed Hat:ansible_automation_platform:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptor-debuginfoRed Hat:ansible_automation_platform:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptor-debugsourceRed Hat:ansible_automation_platform:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
receptorctlRed Hat:ansible_automation_platform:2.5::el9 From an advisory covering 4 CVEs |
before 0:1.4.9-2.el9ap | 0:1.4.9-2.el9ap |
automation-controller-venv-towerRed Hat:ansible_automation_platform:2.5::el8 From an advisory covering 4 CVEs |
before 0:4.6.2-1.el8ap | 0:4.6.2-1.el8ap |
automation-controller-venv-towerRed Hat:ansible_automation_platform:2.5::el9 From an advisory covering 4 CVEs |
before 0:4.6.2-1.el9ap | 0:4.6.2-1.el9ap |
golang-github-lucas-clemente-quic-goUbuntu:22.04:LTS |
All versions, plus listed versions 0.18.0-30.24.0-10.25.0-1 |
None known |
dnscrypt-proxyopenSUSE:Leap 16.0 From an advisory covering 4 CVEs |
before 2.1.16-bp160.1.1 | 2.1.16-bp160.1.1 |
caddySUSE:Package Hub 15 SP5 From an advisory covering 2 CVEs |
before 2.8.4-bp155.2.3.1 | 2.8.4-bp155.2.3.1 |
caddyopenSUSE:Leap 15.5 From an advisory covering 2 CVEs |
before 2.8.4-bp155.2.3.1 | 2.8.4-bp155.2.3.1 |
caddySUSE:Package Hub 15 SP6 From an advisory covering 2 CVEs |
before 2.8.4-bp156.3.3.1 | 2.8.4-bp156.3.3.1 |
caddyopenSUSE:Leap 15.6 From an advisory covering 2 CVEs |
before 2.8.4-bp156.3.3.1 | 2.8.4-bp156.3.3.1 |
corednsSUSE:Package Hub 15 SP6 From an advisory covering 6 CVEs |
before 1.11.3-bp156.4.3.1 | 1.11.3-bp156.4.3.1 |
corednsopenSUSE:Leap 15.6 From an advisory covering 6 CVEs |
before 1.11.3-bp156.4.3.1 | 1.11.3-bp156.4.3.1 |
kuboopenSUSE:Tumbleweed |
before 0.27.0-2.1 | 0.27.0-2.1 |
syncthingopenSUSE:Tumbleweed |
before 1.27.6-1.1 | 1.27.6-1.1 |
corednsopenSUSE:Tumbleweed |
before 1.11.1-5.1 | 1.11.1-5.1 |
caddyopenSUSE:Tumbleweed |
before 2.8.4-1.1 | 2.8.4-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| affected, aliases, references | OSV | |
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2024-22189 is a high vulnerability (CVSS 7.5) in Quic-go, published April 2, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.11%, the 66th percentile. Fixed in github.com/quic-go/quic-go 0.42.0.
References
github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management
youtube.com/watch?v=JqXtYcZAtIA&t=3683s
nvd.nist.gov/vuln/detail/CVE-2024-22189
github.com/advisories/GHSA-c33x-xqrf-c478
Show 41 moreShow less
security.alpinelinux.org/vuln/CVE-2024-22189
github.com/CVEProject/cvelistV5/tree/main/cves/2024/22xxx/CVE-2024-22189.json
security-tracker.debian.org/tracker/CVE-2024-22189
github.com/quic-go/quic-go
access.redhat.com/errata/RHSA-2024:8534
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=2273513
bugzilla.redhat.com/show_bug.cgi?id=2302433
bugzilla.redhat.com/show_bug.cgi?id=2314485
bugzilla.redhat.com/show_bug.cgi?id=2319162
security.access.redhat.com/data/csaf/v2/advisories/2024/rhsa-2024_8534.json
access.redhat.com/security/cve/CVE-2024-10033
cve.org/CVERecord?id=CVE-2024-10033
nvd.nist.gov/vuln/detail/CVE-2024-10033
access.redhat.com/security/cve/CVE-2024-22189
cve.org/CVERecord?id=CVE-2024-22189
access.redhat.com/security/cve/CVE-2024-41989
cve.org/CVERecord?id=CVE-2024-41989
nvd.nist.gov/vuln/detail/CVE-2024-41989
access.redhat.com/security/cve/CVE-2024-45230
cve.org/CVERecord?id=CVE-2024-45230
nvd.nist.gov/vuln/detail/CVE-2024-45230
ubuntu.com/security/CVE-2024-22189
bugzilla.suse.com/1222473
bugzilla.suse.com/1235156
bugzilla.suse.com/1260280
bugzilla.suse.com/1265785
suse.com/security/cve/CVE-2023-49295
suse.com/security/cve/CVE-2024-22189
suse.com/security/cve/CVE-2026-33186
suse.com/security/cve/CVE-2026-33814
lists.opensuse.org/archives/list/[email protected]/thread/4POHOO6U2FW5XKZT7HPGZAJF7LQQW3W4
bugzilla.suse.com/1222468
suse.com/security/cve/CVE-2023-45142
lists.opensuse.org/archives/list/[email protected]/thread/QNDMJCVODSMOIFD655EHBVQRLNUDXLQK
lists.opensuse.org/archives/list/[email protected]/thread/2JLUFKCHWHJJ2MQ6XRREF7D4OOWB23V2
suse.com/security/cve/CVE-2022-27191
suse.com/security/cve/CVE-2022-28948
suse.com/security/cve/CVE-2023-28452
suse.com/security/cve/CVE-2023-30464
suse.com/security/cve/CVE-2024-0874
Left out here: the rest of 4 source descriptions. The JSON record has them.