CVE-2017-16516
Publication date 3 November 2017
Last updated 24 July 2024
Ubuntu priority
Cvss 3 Severity Score
In the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON file is supplied to Yajl::Parser.new.parse, the whole ruby process crashes with a SIGABRT in the yajl_string_decode function in yajl_encode.c. This results in the whole ruby process terminating and potentially a denial of service.
Status
Package | Ubuntu Release | Status |
---|---|---|
ruby-yajl | 24.10 oracular |
Not affected
|
24.04 LTS noble |
Not affected
|
|
22.04 LTS jammy |
Not affected
|
|
20.04 LTS focal |
Not affected
|
|
18.04 LTS bionic |
Not affected
|
|
16.04 LTS xenial |
Vulnerable
|
|
14.04 LTS trusty | Not in release | |
yajl | 24.10 oracular |
Not affected
|
24.04 LTS noble |
Not affected
|
|
22.04 LTS jammy |
Fixed 2.1.0-3ubuntu0.22.04.1
|
|
20.04 LTS focal |
Fixed 2.1.0-3ubuntu0.20.04.1
|
|
18.04 LTS bionic |
Fixed 2.1.0-2ubuntu0.18.04.1~esm1
|
|
16.04 LTS xenial |
Fixed 2.1.0-2ubuntu0.16.04.1~esm1
|
|
14.04 LTS trusty |
Fixed 2.0.4-4ubuntu0.1~esm1
|
Get expanded security coverage with Ubuntu Pro
Reduce your average CVE exposure time from 98 days to 1 day with expanded CVE patching, ten-years security maintenance and optional support for the full stack of open-source applications. Free for personal use.
Get Ubuntu ProNotes
sbeattie
issue in embedded copy of yajl, looks to affect upstream yajl, too
rodrigo-zaiden
as of 2023-06-07, upstream yajl hasn't fixed it, only the embedded copy in ruby-yajl got fixed. even though the code around this fix is similar between yajl and ruby-yajl, the risk of patching one based in the other could be risky without upstream support.
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.5 · High |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | None |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
References
Related Ubuntu Security Notices (USN)
- USN-6233-1
- YAJL vulnerabilities
- 18 July 2023
- USN-6233-2
- YAJL vulnerabilities
- 14 December 2023