Описание
Leptonica through 1.75.3 uses hardcoded /tmp pathnames, which might allow local users to overwrite arbitrary files or have unspecified other impact by creating files in advance or winning a race condition, as demonstrated by /tmp/junk_split_image.ps in prog/splitimage2pdf.c.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | ignored | end of life |
| bionic | ignored | end of standard support, was needed |
| cosmic | released | 1.76.0-1 |
| devel | released | 1.76.0-1 |
| disco | released | 1.76.0-1 |
| eoan | released | 1.76.0-1 |
| esm-apps/bionic | needed | |
| esm-apps/focal | released | 1.76.0-1 |
| esm-apps/jammy | released | 1.76.0-1 |
| esm-apps/noble | released | 1.76.0-1 |
Показывать по
4.4 Medium
CVSS2
7 High
CVSS3
Связанные уязвимости
Leptonica through 1.75.3 uses hardcoded /tmp pathnames, which might allow local users to overwrite arbitrary files or have unspecified other impact by creating files in advance or winning a race condition, as demonstrated by /tmp/junk_split_image.ps in prog/splitimage2pdf.c.
Leptonica through 1.75.3 uses hardcoded /tmp pathnames, which might al ...
Leptonica through 1.75.3 uses hardcoded /tmp pathnames, which might allow local users to overwrite arbitrary files or have unspecified other impact by creating files in advance or winning a race condition, as demonstrated by /tmp/junk_split_image.ps in prog/splitimage2pdf.c.
4.4 Medium
CVSS2
7 High
CVSS3