First published: Wed Dec 13 2023(Updated: )
When a program running on an affected system appends data to a file via an NFS client mount, the bug can cause the NFS client to fail to copy in the data to be written but proceed as though the copy operation had succeeded. This means that the data to be written is instead replaced with whatever data had been in the packet buffer previously. Thus, an unprivileged user with access to an affected system may abuse the bug to trigger disclosure of sensitive information. In particular, the leak is limited to data previously stored in mbufs, which are used for network transmission and reception, and for certain types of inter-process communication. The bug can also be triggered unintentionally by system applications, in which case the data written by the application to an NFS mount may be corrupted. Corrupted data is written over the network to the NFS server, and thus also susceptible to being snooped by other hosts on the network. Note that the bug exists only in the NFS client; the version and implementation of the server has no effect on whether a given system is affected by the problem.
Credit: secteam@freebsd.org
Affected Software | Affected Version | How to fix |
---|---|---|
FreeBSD FreeBSD | =13.2 | |
FreeBSD FreeBSD | =13.2-p1 | |
FreeBSD FreeBSD | =13.2-p2 | |
FreeBSD FreeBSD | =13.2-p3 | |
FreeBSD FreeBSD | =13.2-p4 | |
FreeBSD FreeBSD | =13.2-p5 | |
FreeBSD FreeBSD | =13.2-p6 | |
FreeBSD FreeBSD | =13.2-p7 | |
FreeBSD FreeBSD | =14.0 | |
FreeBSD FreeBSD | =14.0-beta5 | |
FreeBSD FreeBSD | =14.0-p1 | |
FreeBSD FreeBSD | =14.0-p2 | |
FreeBSD FreeBSD | =14.0-rc3 | |
FreeBSD FreeBSD | =14.0-rc4-p1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.