Distribution advisory
This page covers CVE-2024-39908 as tracked by Ubuntu, for the package jruby. The fix is available in version 2.3.1-2~ubuntu16.04.16+esm11; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability low.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: None — an unauthenticated stranger can try it.
- User interaction: Required — someone has to click, open or visit something.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: None.
- Integrity impact: None.
- Availability impact: Low — limited, and the attacker does not choose what is affected.
Weakness class
UBUNTU-CVE-2024-39908 is classified as CWE-400: Uncontrolled Resource Consumption. A request can consume memory, CPU or storage without limit, exhausting capacity for everyone else.
Affected software
UBUNTU-CVE-2024-39908 is recorded against 6 packages.
- jruby
- ruby2.3 (fixed in 2.3.1-2~ubuntu16.04.16+esm11)
- ruby2.5 (fixed in 2.5.1-1ubuntu1.16+esm6)
- ruby2.7 (fixed in 2.7.0-5ubuntu1.16)
- ruby3.0 (fixed in 3.0.2-7ubuntu2.10)
- ruby3.2 (fixed in 3.2.3-1ubuntu0.24.04.5)
Timeline and source
Published on 16 July 2024 and last revised on 20 May 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Report)
www.cve.org (Report)
github.com (Report)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
Other advisories for this package
jruby has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-400: Uncontrolled Resource Consumption) in other software:
