Just in case you didn’t read it, found this one in the archives.
A serious problem in the use of GPG to verify digital signatures has been discovered, which also affects the use of gpg in email. It is possible for an attacker to take any signed message and inject extra arbitrary data without affecting the signed status of the message. Depending on how gpg is invoked, it may be possible to output just faked data as several variants of this attack have been discovered. All versions of gnupg prior to 18.104.22.168 are affected, and it is thus recommended to update GnuPG as soon as possible to version 22.214.171.124
The problem is discussed in full here.
This new problem affects the use of *gpg* for verification of signatures which are _not_ detached signatures. The problem also affects verification of signatures embedded in encrypted messages; i.e. standard use of gpg for mails.
Keep it updated.
- Twitter Bug Bounty Official – Started Paying For Bugs
- Heartbleed Implicated In US Hospital Leak
- XML Quadratic Blowup Attack Blows Up WordPress & Drupal
- Just Crypt It – How To Send A File Securely Without Additional Software
- w3bfukk0r 0.2 Forced Browsing Tool Released
- Browser Security Test – Check Your Browser NOW!
Most Read in Exploits/Vulnerabilities:
- Learn to use Metasploit – Tutorials, Docs & Videos - 227,462 views
- AJAX: Is your application secure enough? - 119,104 views
- eEye Launches 0-Day Exploit Tracker - 85,056 views