Multiple Vendor I/O System Call File Existence Weakness
BID:7279
Info
Multiple Vendor I/O System Call File Existence Weakness
| Bugtraq ID: | 7279 |
| Class: | Design Error |
| CVE: | |
| Remote: | No |
| Local: | Yes |
| Published: | Apr 04 2003 12:00AM |
| Updated: | Apr 04 2003 12:00AM |
| Credit: | The discovery of this weakness has been credited to Andrew Griffiths <[email protected]>. |
| Vulnerable: |
Linux kernel 2.4.20 Linux kernel 2.4.19 Linux kernel 2.4.18 Linux kernel 2.4.17 Linux kernel 2.4.16 Linux kernel 2.4.15 Linux kernel 2.4.14 Linux kernel 2.4.13 Linux kernel 2.4.12 Linux kernel 2.4.11 Linux kernel 2.4.10 Linux kernel 2.4.9 Linux kernel 2.4.8 Linux kernel 2.4.7 Linux kernel 2.4.6 Linux kernel 2.4.5 Linux kernel 2.4.4 Linux kernel 2.4.3 Linux kernel 2.4.2 Linux kernel 2.4.1 Linux kernel 2.4 Linux kernel 2.2.25 Linux kernel 2.2.24 Linux kernel 2.2.23 Linux kernel 2.2.22 Linux kernel 2.2.21 Linux kernel 2.2.20 Linux kernel 2.2.19 Linux kernel 2.2.18 Linux kernel 2.2.17 Linux kernel 2.2.16 Linux kernel 2.2.15 Linux kernel 2.2.14 Linux kernel 2.2.13 Linux kernel 2.2.12 Linux kernel 2.2.11 Linux kernel 2.2.10 Linux kernel 2.2.9 Linux kernel 2.2.8 Linux kernel 2.2.7 Linux kernel 2.2.6 Linux kernel 2.2.5 Linux kernel 2.2.4 Linux kernel 2.2.3 Linux kernel 2.2.2 Linux kernel 2.2.1 Linux kernel 2.2 FreeBSD FreeBSD 4.7 FreeBSD FreeBSD 4.6 FreeBSD FreeBSD 4.5 FreeBSD FreeBSD 4.4 FreeBSD FreeBSD 4.3 FreeBSD FreeBSD 4.2 FreeBSD FreeBSD 4.1 FreeBSD FreeBSD 4.0 |
| Not Vulnerable: | |
Discussion
Multiple Vendor I/O System Call File Existence Weakness
A weakness has been discovered on various systems that may result in an attacker gaining information pertaining to the existence of inaccessible files. The problem lies in the return times when attempting to access existent and non-existent files.
By making requests for various files, it may be possible for an attacker to deduce whether the file exists, by examining the amount of time it takes for an error to be returned.
A weakness has been discovered on various systems that may result in an attacker gaining information pertaining to the existence of inaccessible files. The problem lies in the return times when attempting to access existent and non-existent files.
By making requests for various files, it may be possible for an attacker to deduce whether the file exists, by examining the amount of time it takes for an error to be returned.
Exploit / POC
Multiple Vendor I/O System Call File Existence Weakness
A proof of concept exploit has been released by Andrew Griffiths.
A proof of concept exploit has been released by Andrew Griffiths.
Solution / Fix
Multiple Vendor I/O System Call File Existence Weakness
Solution:
It should be noted that a fix for this weakness might not be plausible on all systems, as the problem may lie in the efficiency of computation and not in specific system call implementation.
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
It should be noted that a fix for this weakness might not be plausible on all systems, as the problem may lie in the efficiency of computation and not in specific system call implementation.
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
References
Multiple Vendor I/O System Call File Existence Weakness
References:
References:
- Syscall implementation could lead to whether or not a file exists (Andrew Griffiths