Skip to content
Fencer Intel
medium 6.5

CVE-2022-3433 json

Hash flooding vulnerability in aeson

published 4y ago modified 4mo ago also EUVD-2022-42809 , HSEC-2023-0001

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

The aeson library is not safe to use to consume untrusted JSON input. A remote user could abuse this flaw to produce a hash collision in the underlying unordered-containers library by sending specially crafted JSON data, resulting in a denial of service.

Patch / fix

  • hackage aeson 2.0.1.0
  • haskell aeson 2.0.1.0
  • haskell-aeson Debian 14, Debian 13, Debian 12 2.0.3.0-1

debian advisories DEBIAN-CVE-2022-3433

Is CVE-2022-3433 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-3433 updated cvss 7.5

ghc-aeson: untrusted JSON input leads to hash collisions and DoS

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • cs-syd.eu https://cs-syd.eu/posts/2021-09-11-json-vulnerability referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
hackage aeson
>=0.4.0.0, <2.0.1.0
2.0.1.0

Affected products

  • n/a aeson

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.