CVE-2017-16516

high

Published 2017-11-03 · Modified 2024-02-16

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS v4 NEW

—

not yet in upstream

VIR risk

7.5

Description

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.

Predictions

Exploit likelihood

83%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OS	Version	Status	Fixed in
debian	bullseye	fixed	`1.2.0-3.1`
debian	forky	fixed	`3.1.4-2`
debian	sid	fixed	`3.1.4-2`
debian	trixie	fixed	`3.1.4-2`
sles		affected
debian	bookworm	fixed	`0`
debian	7.0	affected

Package impact

Ecosystem	Package	Vulnerable	Fixed
RubyGems	yajl-ruby	`<>= 1.3.1`	`>= 1.3.1`
RubyGems	yajl-ruby	`<1.3.1`	`1.3.1`

Application impact

Vendor	Product	Versions	Fixed
yajl-ruby_project	yajl-ruby	`1.3.0`

References

CWEs

CWE-134

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.