CVE-2004-2613: Critical severity vserver Linux-VServer vulnerability

Published Dec 31, 2004
·
Updated

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.

Affected Software

8 affected components
vserver Linux-VServer=1.3.0
vserver Linux-VServer=1.3.1
vserver Linux-VServer=1.3.2
vserver Linux-VServer=1.3.3
vserver Linux-VServer=1.3.4
vserver Linux-VServer=1.20
vserver Linux-VServer=1.21
vserver Linux-VServer=1.22

Remediation

Event History

Dec 31, 2004
CVE Published
05:00 AM
Dec 4, 2005
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2004-2613?

The severity of CVE-2004-2613 is currently unspecified.

2

How do I fix CVE-2004-2613?

To fix CVE-2004-2613, users should upgrade to a version of Linux-VServer that is 1.3.5 or later.

3

What versions are affected by CVE-2004-2613?

CVE-2004-2613 affects Linux-VServer versions prior to 1.3.5.

4

Can CVE-2004-2613 be exploited remotely?

The attack vectors for CVE-2004-2613 are unspecified, making it unclear if remote exploitation is possible.

5

Is CVE-2004-2613 related to any specific proc entries?

Yes, CVE-2004-2613 involves write access to specific proc entries from a vserver context.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203