CVE-2023-49295

quic-go is an implementation of the QUIC protocol (RFC 9000, RFC 9001, RFC 9002) in Go. An attacker can cause its peer to run out of memory sending a large number of PATH_CHALLENGE frames. The receiver is supposed to respond to each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prevent the receiver from sending out (the vast majority of) these PATH_RESPONSE frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. This vulnerability has been patched in versions 0.37.7, 0.38.2 and 0.39.4.

quic-go is an implementation of the QUIC protocol (RFC 9000, RFC 9001, RFC 9002) in Go. An attacker can cause its peer to run out of memory sending a large number of PATH_CHALLENGE frames. The receiver is supposed to respond to each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prevent the receiver from sending out (the vast majority of) these PATH_RESPONSE frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. This vulnerability has been patched in versions 0.37.7, 0.38.2 and 0.39.4.

An attacker can cause its peer to run out of memory sending a large number of PATH_CHALLENGE frames. The receiver is supposed to respond to each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prevent the receiver from sending out (the vast majority of) these PATH_RESPONSE 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/2023-12-18-exploiting-quics-path-validation/

There's no way to mitigate this attack, please update quic-go to a version that contains the fix.

quic-go is an implementation of the QUIC protocol (RFC 9000, RFC 9001, RFC 9002) in Go. An attacker can cause its peer to run out of memory sending a large number of PATH_CHALLENGE frames. The receiver is supposed to respond to each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prevent the receiver from sending out (the vast majority of) these PATH_RESPONSE frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. This vulnerability has been patched in versions 0.37.7, 0.38.2 and 0.39.4.

Denial of service via path validation in github.com/quic-go/quic-go

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 $DHCP syntax
  • 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: clear properly 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.…

These are all security issues fixed in the syncthing-1.27.2-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the kubo-0.32.1-1.1 package on the GA media of openSUSE Tumbleweed.