High · published May 30, 2006
Stack-based buffer overflow in the tiffsplit command in libtiff 3.8.2 and earlier might might allow attackers to execute arbitrary code via a long filename. NOTE: tiffsplit is not setuid. If there is not a common scenario under which tiffsplit is called with attacker-controlled command line arguments, then perhaps this issue should not be included in CVE.
| Product | Versions | Fixed in |
|---|---|---|
| libtiff/libtiff | ≤ 3.8.2 | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |
| libtiff/libtiff | all versions | — |