Bug 1442099 (CVE-2017-7467) - CVE-2017-7467 minicom: Out of bounds write in vt100.c
Summary: CVE-2017-7467 minicom: Out of bounds write in vt100.c
Alias: CVE-2017-7467
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1443129
Blocks: 1442106
TreeView+ depends on / blocked
Reported: 2017-04-13 13:55 UTC by Adam Mariš
Modified: 2021-02-17 02:19 UTC (History)
5 users (show)

Fixed In Version: minicom 2.7.1
Doc Type: If docs needed, set a value
Doc Text:
A buffer overflow flaw was found in the way minicom handled VT100 escape sequences. A malicious terminal device could potentially use this flaw to crash minicom, or execute arbitrary code in the context of the minicom process.
Clone Of:
Last Closed: 2017-04-20 04:42:16 UTC

Attachments (Terms of Use)

Description Adam Mariš 2017-04-13 13:55:51 UTC
A potentially exploitable out of bounds write vulnerability in vt100.c was found.

Vulnerable code:

static void (*vt_keyb)(int, int);/* Gets called for NORMAL/APPL switch. */
static void (*termout)(const char *, int);/* Gets called to output a string. */

static int escparms[8];         /* Cumulated escape sequence. */
static int ptr;                 /* Index into escparms array. */
static long vt_tabs[5];         /* Tab stops for max. 32*5 = 160 columns. */


  /* See if a number follows */
  if (c >= '0' && c <= '9') {
    escparms[ptr] = 10*escparms[ptr] + c - '0';
  /* Separation between numbers ? */
  if (c == ';') {
    if (ptr < 15)

With crafted input, attacker can write out of bounds of escparms array and could potentially overwrite ptr pointer.

Comment 1 Adam Mariš 2017-04-13 13:55:55 UTC

Name: Alexander Peslyak (Openwall)

Comment 5 Dhiru Kholia 2017-04-18 14:12:59 UTC
Created minicom tracking bugs for this issue:

Affects: fedora-all [bug 1443129]

Comment 6 Dhiru Kholia 2017-04-18 14:17:49 UTC
Public via http://www.openwall.com/lists/oss-security/2017/04/18/5

Note You need to log in before you can comment on or make changes to this bug.