Strix
26.1K

CVE-2005-4798

UnknownEPSS 2.95%

Last modified

CVE-2005-4798 is a vulnerability of currently unknown severity. Buffer overflow in NFS readlink handling in the Linux Kernel 2.4 up to 2.4.31 allows remote NFS servers to cause a denial of service (crash) via a long symlink, which is not properly handled in (1) nfs2xdr.c or (2) nfs3xdr.c and causes a crash in the NFS client.. EPSS estimates a 2.95% chance of exploitation in the next 30 days.

Description

Buffer overflow in NFS readlink handling in the Linux Kernel 2.4 up to 2.4.31 allows remote NFS servers to cause a denial of service (crash) via a long symlink, which is not properly handled in (1) nfs2xdr.c or (2) nfs3xdr.c and causes a crash in the NFS client.

Metrics

EPSS Probability
2.95%

85.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
LinuxLinux Kernel2.4.0
LinuxLinux Kernel2.4.1
LinuxLinux Kernel2.4.2
LinuxLinux Kernel2.4.3
LinuxLinux Kernel2.4.10
LinuxLinux Kernel2.4.11
LinuxLinux Kernel2.4.12
LinuxLinux Kernel2.4.13
LinuxLinux Kernel2.4.14
LinuxLinux Kernel2.4.15
LinuxLinux Kernel2.4.16
LinuxLinux Kernel2.4.17
LinuxLinux Kernel2.4.18
LinuxLinux Kernel2.4.19
LinuxLinux Kernel2.4.20
LinuxLinux Kernel2.4.21
LinuxLinux Kernel2.4.22
LinuxLinux Kernel2.4.23
LinuxLinux Kernel2.4.23_ow2
LinuxLinux Kernel2.4.24
LinuxLinux Kernel2.4.24_ow1
LinuxLinux Kernel2.4.25
LinuxLinux Kernel2.4.26
LinuxLinux Kernel2.4.27
LinuxLinux Kernel2.4.28
LinuxLinux Kernel2.4.29
LinuxLinux Kernel2.4.30

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2005-4798?
Buffer overflow in NFS readlink handling in the Linux Kernel 2.4 up to 2.4.31 allows remote NFS servers to cause a denial of service (crash) via a long symlink, which is not properly handled in (1) nfs2xdr.c or (2) nfs3xdr.c and causes a crash in the NFS client.
How severe is CVE-2005-4798?
Severity scoring for CVE-2005-4798 is pending analysis. The EPSS model estimates a 2.95% probability of exploitation in the next 30 days.
How do I fix CVE-2005-4798?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2005

View all 2005CVEs →

Are you affected by CVE-2005-4798?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST