CVE-2008-1845 json
The Korn shell (aka mksh) before R33d on MirOS (aka MirBSD) does not flush the tty's I/O when invoking mksh in a new terminal, which allows…
published 2008-04-16 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1845
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
The Korn shell (aka mksh) before R33d on MirOS (aka MirBSD) does not flush the tty's I/O when invoking mksh in a new terminal, which allows local users to gain privileges by opening a virtual terminal and entering command sequences, which might later be executed in opportunistic circumstances by a different user who launches mksh and specifies that terminal with the -T option.
Patch / fix
- mksh Debian 14, Debian 13, Debian 12 33.4-1
debian advisories DEBIAN-CVE-2008-1845
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2008-1845 updated
mksh: privilege escalation via unflushed tty
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
secunia.com
/advisories/29803
third-party-advisory, vendor-advisory
-
osvdb.org
/44365
vdb-entry
-
securityfocus.com
/bid/28768
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41794
vdb-entry
- mirbsd.org /mksh.htm#clog
Sources
- CVE List CVE-2008-1845
- NVD CVE-2008-1845
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.