3 ms·
Well crap, now I have yet another reason to lose sleep tonight. I always thought Vim and text-files were safe. I do find something endlessly interesting in th
by tombert 7y ago
Well crap, now I have yet another reason to lose sleep tonight. I always thought Vim and text-files were safe.
I do find something endlessly interesting in these kinds of vulnerabilities, for no other reason than the fact that I can appreciate the hunt for them. I wouldn't really think to look at Vim as an attack vector, and even if I did, I wouldn't even know where to start.
- gowld 7y agoThe article cites security bugs in bugs from 2016 and 2002
- cjbprime 7y agoCheck this one out, then: http://www.h-online.com/security/news/item/Xterm-terminal-emulator-executes-injected-commands-739557.html http://www.h-online.com/security/news/item/Xterm-terminal-em...
- cyphar 7y agoGiven that most administrators use vim to edit everything in the system and often open random files, I would think vim is the most obvious thing to attack (just like printers in corporate networks). Just do "set nomodeline" and move on. I've had it disabled for the past ~10 years because of previous CVEs like this (such as CVE-2007-2438).
- lloeki 7y agoor use https://github.com/ciaranm/securemodelines https://github.com/ciaranm/securemodelines like I did for the past aeon