It was discovered that Vim incorrectly handled memory when opening certain files. If an attacker could trick a user into opening a specially crafted file, it could cause Vim to crash, or possible execute arbitrary code.
{ "availability": "Available with Ubuntu Pro: https://ubuntu.com/pro", "binaries": [ { "vim-gui-common": "2:7.4.1689-3ubuntu1.5+esm8", "vim-gtk-py2": "2:7.4.1689-3ubuntu1.5+esm8", "vim-tiny": "2:7.4.1689-3ubuntu1.5+esm8", "vim-gtk": "2:7.4.1689-3ubuntu1.5+esm8", "vim-athena": "2:7.4.1689-3ubuntu1.5+esm8", "vim-nox": "2:7.4.1689-3ubuntu1.5+esm8", "vim-doc": "2:7.4.1689-3ubuntu1.5+esm8", "vim-gnome": "2:7.4.1689-3ubuntu1.5+esm8", "vim": "2:7.4.1689-3ubuntu1.5+esm8", "vim-gnome-py2": "2:7.4.1689-3ubuntu1.5+esm8", "vim-athena-py2": "2:7.4.1689-3ubuntu1.5+esm8", "vim-common": "2:7.4.1689-3ubuntu1.5+esm8", "vim-gtk3-py2": "2:7.4.1689-3ubuntu1.5+esm8", "vim-gtk3": "2:7.4.1689-3ubuntu1.5+esm8", "vim-nox-py2": "2:7.4.1689-3ubuntu1.5+esm8", "vim-runtime": "2:7.4.1689-3ubuntu1.5+esm8" } ] }