CVE-2022-24795: Buffer Overflow and Integer Overflow in yajl-ruby
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.4% (FIRST EPSS); higher than 89% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: yajl (AlmaLinux:8) 2.1.0-11.el8; yajl-devel (AlmaLinux:8) 2.1.0-11.el8; yajl (AlmaLinux:9) 2.1.0-21.el9.
Low priority for now. Upgrade to yajl (AlmaLinux:8) 2.1.0-11.el8; yajl-devel (AlmaLinux:8) 2.1.0-11.el8; yajl (AlmaLinux:9) 2.1.0-21.el9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
yajl-ruby is a C binding to the YAJL JSON parsing and generation library. The 1.x branch and the 2.x branch of `yajl` contain an integer overflow which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. The reallocation logic at `yajl_buf.c#L64` may result in the `need` 32bit integer wrapping to 0 when `need` approaches a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation of buf->alloc into a small heap chunk. These integers are declared as `size_t` in the 2.x branch of `yajl`, which practically prevents the issue from triggering on 64bit platforms, however this does not preclude this issue triggering on 32bit builds on which `size_t` is a 32bit integer. Subsequent population of this under-allocated heap chunk is based on the original buffer size, leading to heap memory corruption. This vulnerability mostly impacts process availability. Maintainers believe exploitation for arbitrary code execution is unlikely. A patch is available and anticipated to be part of yajl-ruby version 1.4.2. As a workaround, avoid passing large inputs to YAJL.
- Published
- Apr 5, 2022
- Updated
- Jun 17, 2026
- EPSS
- 3.4% · 89th percentile
- CWE
- CWE-122
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 5.9
- 1.6 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| yajl-ruby project | yajl-ruby | cpe:2.3:a:yajl-ruby_project:yajl-ruby |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- yajl-ruby project yajl-rubybefore 1.4.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
brianmario yajl-ruby
- <= 1.4.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | yajl | before 2.1.0-11.el8 | 2.1.0-11.el8 |
| AlmaLinux:8 | yajl-devel | before 2.1.0-11.el8 | 2.1.0-11.el8 |
| AlmaLinux:9 | yajl | before 2.1.0-21.el9 | 2.1.0-21.el9 |
| AlmaLinux:9 | yajl-devel | before 2.1.0-21.el9 | 2.1.0-21.el9 |
| Debian:10 | burp | before 2.1.32-2+deb10u1 | 2.1.32-2+deb10u1 |
| Debian:10 | yajl | before 2.1.0-3+deb10u2 | 2.1.0-3+deb10u2 |
| Debian:12 | burp | from 0 | — |
| Debian:12 | r-cran-jsonlite | from 0 | — |
| Debian:12 | ruby-yajl | before 1.4.3-1 | 1.4.3-1 |
| Debian:12 | yajl | before 2.1.0-3+deb12u2 | 2.1.0-3+deb12u2 |
| Debian:13 | burp | before 3.1.4-2 | 3.1.4-2 |
| Debian:13 | r-cran-jsonlite | before 1.8.8+dfsg-1 | 1.8.8+dfsg-1 |
| Debian:13 | yajl | before 2.1.0-4 | 2.1.0-4 |
| openSUSE:Leap Micro 5.2 | libyajl | before 2.1.0-150000.4.3.1 | 2.1.0-150000.4.3.1 |
| Red Hat:enterprise_linux:8::appstream | yajl | before 0:2.1.0-11.el8 | 0:2.1.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | yajl-debuginfo | before 0:2.1.0-11.el8 | 0:2.1.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | yajl-debugsource | before 0:2.1.0-11.el8 | 0:2.1.0-11.el8 |
| Red Hat:enterprise_linux:8::crb | yajl-devel | before 0:2.1.0-11.el8 | 0:2.1.0-11.el8 |
| Red Hat:enterprise_linux:9::appstream | yajl | before 0:2.1.0-21.el9 | 0:2.1.0-21.el9 |
| Red Hat:enterprise_linux:9::appstream | yajl-debuginfo | before 0:2.1.0-21.el9 | 0:2.1.0-21.el9 |
| Red Hat:enterprise_linux:9::appstream | yajl-debugsource | before 0:2.1.0-21.el9 | 0:2.1.0-21.el9 |
| Red Hat:enterprise_linux:9::crb | yajl-devel | before 0:2.1.0-21.el9 | 0:2.1.0-21.el9 |
| Red Hat:rhel_eus:8.6::appstream | yajl | before 0:2.1.0-13.el8_6 | 0:2.1.0-13.el8_6 |
| Red Hat:rhel_eus:8.6::appstream | yajl-debuginfo | before 0:2.1.0-13.el8_6 | 0:2.1.0-13.el8_6 |
+9
Same product
yajl-ruby project: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-16516In 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 S31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:yajl | 2.1.0-11.el8 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:yajl-devel | 2.1.0-11.el8 · AlmaLinux:8 | Package registry (OSV) |
| debian:burp | 3.1.4-2 · Debian:13 | Package registry (OSV) |
| debian:r-cran-jsonlite | 1.8.8+dfsg-1 · Debian:13 | Package registry (OSV) |
| debian:ruby-yajl | 1.4.3-1 · Debian:12 | Package registry (OSV) |
| debian:yajl | 2.1.0-3+deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:libyajl | 2.1.0-150000.4.3.1 · openSUSE:Leap Micro 5.2 | Package registry (OSV) |
| red hat:yajl | 0:2.1.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:yajl-debuginfo | 0:2.1.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:yajl-debugsource | 0:2.1.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:yajl-devel | 0:2.1.0-11.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| rocky linux:yajl | 0:2.1.0-11.el8 · Rocky Linux:8 | Package registry (OSV) |
| RubyGems:yajl-ruby | 1.4.3 | Package registry (OSV) |
| suse:libyajl | 2.0.1-18.7.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:libyajl | 2.1.0-150000.4.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
| suse:rubygem-yajl-ruby | 1.3.1-4.6.1 · SUSE:OpenStack Cloud Crowbar 8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
- lists.debian.org/debian-lts-announce/2023/07/msg00013.html
- lists.debian.org/debian-lts-announce/2023/08/msg00003.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KLE3C4CECEJ4EUYI56KXI6OWACWXX7WN/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YO32YDJ74DADC7CMJNLSLBVWN5EXGF5J/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.