CWE
22
EPSS
0.047%
Advisory Published
Updated

CVE-2024-6759: NFS client accepts file names containing path separators

First published: Sun Aug 11 2024(Updated: )

When mounting a remote filesystem using NFS, the kernel did not sanitize remotely provided filenames for the path separator character, "/". This allows readdir(3) and related functions to return filesystem entries with names containing additional path components. The lack of validation described above gives rise to a confused deputy problem. For example, a program copying files from an NFS mount could be tricked into copying from outside the intended source directory, and/or to a location outside the intended destination directory.

Credit: secteam@freebsd.org

Affected SoftwareAffected VersionHow to fix
FreeBSD Kernel<13.0
FreeBSD Kernel>=13.1<13.3
FreeBSD Kernel=13.3-p1
FreeBSD Kernel=13.3-p2
FreeBSD Kernel=13.3-p3
FreeBSD Kernel=13.3-p4
FreeBSD Kernel=14.0-beta5
FreeBSD Kernel=14.0-p1
FreeBSD Kernel=14.0-p2
FreeBSD Kernel=14.0-p3
FreeBSD Kernel=14.0-p4
FreeBSD Kernel=14.0-p5
FreeBSD Kernel=14.0-p6
FreeBSD Kernel=14.0-p7
FreeBSD Kernel=14.0-p8
FreeBSD Kernel=14.0-rc3
FreeBSD Kernel=14.0-rc4-p1
FreeBSD Kernel=14.1-p1
FreeBSD Kernel=14.1-p2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-6759?

    CVE-2024-6759 has been classified with a high severity level due to its potential impact on filesystem security.

  • How do I fix CVE-2024-6759?

    To mitigate CVE-2024-6759, users should apply the recommended patches released by FreeBSD for affected versions.

  • What versions of FreeBSD are affected by CVE-2024-6759?

    CVE-2024-6759 affects FreeBSD versions 13.0, 13.1 through 13.3, and several versions of 14.x, including beta and release candidates.

  • What issues does CVE-2024-6759 cause in FreeBSD?

    CVE-2024-6759 allows readdir(3) and related functions to return filesystem entries with names containing additional path components, leading to potential security risks.

  • What should I do if I can't immediately patch CVE-2024-6759?

    If immediate patching is not possible for CVE-2024-6759, consider restricting access to affected systems and monitoring for unusual activity until a fix can be applied.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203