On an msdosfs filesystem, the truncate or ftruncate system calls under certain circumstances populate the additional space in the file with unallocated data from the underlying disk device, rather than zero bytes.
This may permit a user with write access to files on a msdosfs filesystem to read unintended data (e.g. from a previously deleted file).
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Freebsd | Freebsd | * | 12.4 (excluding) |
| Freebsd | Freebsd | 13.0 (including) | 13.2 (excluding) |
| Freebsd | Freebsd | 12.4 (including) | 12.4 (including) |
| Freebsd | Freebsd | 12.4-p1 (including) | 12.4-p1 (including) |
| Freebsd | Freebsd | 12.4-p2 (including) | 12.4-p2 (including) |
| Freebsd | Freebsd | 12.4-p3 (including) | 12.4-p3 (including) |
| Freebsd | Freebsd | 12.4-p4 (including) | 12.4-p4 (including) |
| Freebsd | Freebsd | 12.4-p5 (including) | 12.4-p5 (including) |
| Freebsd | Freebsd | 13.2 (including) | 13.2 (including) |
| Freebsd | Freebsd | 13.2-p1 (including) | 13.2-p1 (including) |
| Freebsd | Freebsd | 13.2-p2 (including) | 13.2-p2 (including) |
| Freebsd | Freebsd | 13.2-p3 (including) | 13.2-p3 (including) |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.