Affected versions
Ubuntu16.04:LTS/jruby
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu18.04:LTS/jruby
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu22.04:LTS/ruby3.0
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu24.04:LTS/ruby3.2
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu25.10/jruby
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu25.10/ruby3.3
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu26.04:LTS/ruby3.3
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu26.10/jruby
- Affected versions
- *
- Fixed version
- Not reported
Ubuntu26.10/ruby3.3
- Affected versions
- *
- Fixed version
- Not reported
UbuntuPro:14.04:LTS/jruby
- Affected versions
- *
- Fixed version
- Not reported
UbuntuPro:16.04:LTS/ruby2.3
- Affected versions
- *
- Fixed version
- Not reported
UbuntuPro:18.04:LTS/ruby2.5
- Affected versions
- *
- Fixed version
- Not reported
UbuntuPro:20.04:LTS/ruby2.7
- Affected versions
- *
- Fixed version
- Not reported
Description
An issue was discovered in Ruby 4 before 4.0.5. A race condition leading to a use-after-free in the pthread-based getaddrinfo timeout handler (rb_getaddrinfo in ext/socket/raddrinfo.c) allows a remote attacker who can delay DNS responses near the user-specified timeout to crash a Ruby process that calls Addrinfo.getaddrinfo(..., timeout:) or Socket.tcp(..., resolv_timeout:). Memory-corruption-based exploitation is theoretically possible. The attack could, for example, be carried out through a crafted authoritative DNS server or recursive resolver.

