Notepad++ Update Fixes 'CIA Hacking' Issue (archive.org)
Free software Notepad++ (released under the GNU General Public License) received a new update this week which was announced under the headline "Fix CIA Hacking Notepad++ Issue". The CIA documents in WikiLeaks' 'Vault 7' included a "Notepad++ DLL Hijack" document which affected the popular Windows editor for text and source code. "It's not a vulnerability/security issue in Notepad++, but for remedying this issue, from this release (v7.3.3) forward, notepad++.exe checks the certificate validation in scilexer.dll before loading it," reads the announcement. From the Notepad++ web site:
If the certificate is missing or invalid, then it just won't be loaded, and Notepad++ will fail to launch. Checking the certificate of DLL makes it harder to hack.
Note that once users' PCs are compromised, the hackers can do anything on the PCs. This solution only prevents from Notepad++ loading a CIA homemade DLL. It doesn't prevent your original notepad++.exe from being replaced by modified notepad++.exe while the CIA is controlling your PC.
The update also includes "a lot of enhancements and bug-fixes," and if no critical issues are found, "Auto-updater will be triggered in few days."
Note that once users' PCs are compromised, the hackers can do anything on the PCs. This solution only prevents from Notepad++ loading a CIA homemade DLL. It doesn't prevent your original notepad++.exe from being replaced by modified notepad++.exe while the CIA is controlling your PC.
The update also includes "a lot of enhancements and bug-fixes," and if no critical issues are found, "Auto-updater will be triggered in few days."
It helps knowing all those things. Now, whoever isn't lazy/incompetent/in bed with the CIA will implement required changes to eliminate vulnerabilities.
...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
This is why I still do all of my development work in edlin.
I just use cat. I guess Ed is secure too since no one else's it anymore
http://saveie6.com/
In peace and freedom loving USA secret police hack you and your TV and phone and car and computer.
"... punched tape..."
Punched tape!!! Some people have to jump on new technology. I engrave characters in stone. Let the CIA try to modify that remotely.
From the Notepad++ page (and even the Slashdot summary): "Note that once usersâ(TM) PCs are compromised, the hackers can do anything on the PCs."
Repeat after me: If my computer is compromised, there's nothing that any individual app on the system can do to protect itself from being hijacked.
There's nothing to see here.
You can get decent OCR software for Windows; open-source substitutes are laughable when you look at their error rates.
The CIA had to get me to install and register a malicious DLL. If they can get me to do that then they can do worse than this. It just seems like the DLL is a place for them to have hidden a malicious payload. They could have chosen a number of other places and likely will just switch now.
This isn't a hack of notepad++
http://web.archive.org/web/201...
APK will save me with shadow stacks!
Got mixed feelings about this. There's a real security risk that this would help a lot with. But... user desires and code bloat always expand to take all available resources. So, there is a downside.
What if the executable itself is compromised? Really, we need a coherent philosophy re digital signing. Do we cede control to the owners of the certificates, or to hackers? I say neither. If the signature is broken, always inform the user and always let the user make a command decision.
If the owner of a host signs his own executables, that's fine - if he builds them himself from source. Make sure we allow this on all binaries. Don't mandate a particular signing authority. But then we must inform always inform the user at runtime just who signed what he's about to load. Because hackers can sign, too.
Informed consent, and the user beware.