Michael Jennings maintains a narrow product portfolio centered on Eterm, a terminal emulator with a modest but durable vulnerability footprint. The vendor's disclosures frequently acquire public exploit tooling, reflecting the appeal of terminal software to attackers seeking execution and persistence on user systems. Current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Michael Jennings over time
Signals from CVEs in this vendor scope (6 CVEs).
6 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2000-0476MEDIUM xterm, Eterm, and rxvt allow an attacker to cause a denial of service by embedding certain escape characters which force the window to be resized. | Jun 1, 2000 | 5.0 | 25 | NO | YES |
CVE-2003-0068HIGH The Eterm terminal emulator 0.9.1 and earlier allows attackers to modify the window title via a certain character escape sequence and then insert it back to the command line in the | Mar 3, 2003 | 7.5 | 21 | NO | NO |
CVE-2002-0143MEDIUM Buffer overflow in Eterm of Enlightenment Imlib2 1.0.4 and earlier allows local users to execute arbitrary code via a long HOME environment variable. | Mar 25, 2002 | 4.6 | 21 | NO | YES |
CVE-2000-0367HIGH Vulnerability in eterm 0.8.8 in Debian GNU/Linux allows an attacker to gain root privileges. | Feb 18, 1999 | 7.2 | 20 | NO | NO |
CVE-2003-0021MEDIUM The "screen dump" feature in Eterm 0.9.1 and earlier allows attackers to overwrite arbitrary files via a certain character escape sequence when it is echoed to a user's terminal, e | Mar 3, 2003 | 5.0 | 15 | NO | NO |
CVE-2003-0382MEDIUM Buffer overflow in Eterm 0.9.2 allows local users to gain privileges via a long ETERMPATH environment variable. | Jul 2, 2003 | 4.6 | 14 | NO | NO |
Signals from CVEs in this vendor scope (6 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Michael Jennings.
Media articles that mention a CVE ID that affects a product developed by Michael Jennings — matched by CVE ID, not by vendor name.