CVE-2004-2001: Medium severity sgi irix vulnerability
Published May 5, 2004
·Updated
ifconfig "-arp" in SGI IRIX 6.5 through 6.5.22m does not properly disable ARP requests from being sent or received.
Affected Software
28 affected components
SGI IRIX=6.5.6
SGI IRIX=6.5.17f
SGI IRIX=6.5.1
SGI IRIX=6.5.10
SGI IRIX=6.5.12
SGI IRIX=6.5.18f
SGI IRIX=6.5.19f
SGI IRIX=6.5.21f
SGI IRIX=6.5.9
SGI IRIX=6.5.21m
SGI IRIX=6.5.17m
SGI IRIX=6.5.20m
SGI IRIX=6.5.15
SGI IRIX=6.5.3
SGI IRIX=6.5.14
SGI IRIX=6.5.8
SGI IRIX=6.5.22m
SGI IRIX=6.5.19m
SGI IRIX=6.5.20f
SGI IRIX=6.5.5
SGI IRIX=6.5.4
SGI IRIX=6.5.11
SGI IRIX=6.5.2
SGI IRIX=6.5
SGI IRIX=6.5.7
SGI IRIX=6.5.18m
SGI IRIX=6.5.13
SGI IRIX=6.5.16
Remediation
Patch Available
Event History
May 5, 2004
CVE Published
04:00 AM
May 10, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2004-2001?
CVE-2004-2001 is classified as a medium severity vulnerability.
2
How do I fix CVE-2004-2001?
To fix CVE-2004-2001, you should upgrade to an unaffected version of SGI IRIX, specifically 6.5.23 or later.
3
What software is affected by CVE-2004-2001?
CVE-2004-2001 affects SGI IRIX versions 6.5 through 6.5.22m.
4
What happens if CVE-2004-2001 is exploited?
If exploited, CVE-2004-2001 can allow unauthorized ARP requests, potentially compromising network security.
5
Is there a workaround for CVE-2004-2001?
There is no official workaround for CVE-2004-2001; upgrading to a fixed version is the only resolution.