renameat(2) did not enforce FD_RESOLVE_BENEATH on its directory arguments. A jailed process could rename a directory relative to a restricted descriptor, then escape the jail root via fchdir(2). This requires the directory to reside on a filesystem that is also reachable from the jails root.
A process in a jail that has received a directory file descriptor from another jail can use these techniques to escape the jails filesystem root restriction.
Weakness
The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Freebsd | Freebsd | 14.4 (including) | 14.4 (including) |
| Freebsd | Freebsd | 14.4-p1 (including) | 14.4-p1 (including) |
| Freebsd | Freebsd | 14.4-p2 (including) | 14.4-p2 (including) |
| Freebsd | Freebsd | 14.4-p3 (including) | 14.4-p3 (including) |
| Freebsd | Freebsd | 14.4-p4 (including) | 14.4-p4 (including) |
| Freebsd | Freebsd | 14.4-p5 (including) | 14.4-p5 (including) |
| Freebsd | Freebsd | 14.4-p6 (including) | 14.4-p6 (including) |
| Freebsd | Freebsd | 14.4-p7 (including) | 14.4-p7 (including) |
| Freebsd | Freebsd | 14.4-p8 (including) | 14.4-p8 (including) |
| Freebsd | Freebsd | 14.4-p9 (including) | 14.4-p9 (including) |
| Freebsd | Freebsd | 14.5 (including) | 14.5 (including) |
| Freebsd | Freebsd | 15.0 (including) | 15.0 (including) |
| Freebsd | Freebsd | 15.0-p1 (including) | 15.0-p1 (including) |
| Freebsd | Freebsd | 15.0-p10 (including) | 15.0-p10 (including) |
| Freebsd | Freebsd | 15.0-p11 (including) | 15.0-p11 (including) |
| Freebsd | Freebsd | 15.0-p12 (including) | 15.0-p12 (including) |
| Freebsd | Freebsd | 15.0-p13 (including) | 15.0-p13 (including) |
| Freebsd | Freebsd | 15.0-p2 (including) | 15.0-p2 (including) |
| Freebsd | Freebsd | 15.0-p3 (including) | 15.0-p3 (including) |
| Freebsd | Freebsd | 15.0-p4 (including) | 15.0-p4 (including) |
| Freebsd | Freebsd | 15.0-p5 (including) | 15.0-p5 (including) |
| Freebsd | Freebsd | 15.0-p6 (including) | 15.0-p6 (including) |
| Freebsd | Freebsd | 15.0-p7 (including) | 15.0-p7 (including) |
| Freebsd | Freebsd | 15.0-p8 (including) | 15.0-p8 (including) |
| Freebsd | Freebsd | 15.0-p9 (including) | 15.0-p9 (including) |
| Freebsd | Freebsd | 15.1 (including) | 15.1 (including) |
| Freebsd | Freebsd | 15.1-p1 (including) | 15.1-p1 (including) |
| Freebsd | Freebsd | 15.1-p2 (including) | 15.1-p2 (including) |
| Freebsd | Freebsd | 15.1-p3 (including) | 15.1-p3 (including) |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.