From the source : We discovered a way to inject data through the passphrase property of the gnupg.GPG.encrypt() and gnupg.GPG.decrypt() methods when symmetric encryption is used. The supplied passphrase is not validated for newlines, and the library passes --passphrase-fd=0 to the gpg executable, which expects the passphrase on the first line of stdin, and the ciphertext to be decrypted or plaintext to be encrypted on subsequent lines. By supplying a passphrase containing a newline an attacker can control/modify the ciphertext/plaintext being decrypted/encrypted. Vulnerable in: python-gnupg 0.4.3 and maybe earlier versions. Mitigation : Users should upgrade to python-gnupg 0.4.4 Upstream : https://github.com/stigtsp/CVE-2019-6690-python-gnupg-vulnerability https://github.com/vsajip/python-gnupg/commit/39eca266dd837e2ad89c94eb17b7a6f50b25e7cf#diff-88b99bb28683bd5b7e3a204826ead112 https://github.com/vsajip/python-gnupg/commit/3003b654ca1c29b0510a54b9848571b3ad57df19#diff-88b99bb28683bd5b7e3a204826ead112 References : https://blog.hackeriet.no/cve-2019-6690-python-gnupg-vulnerability/ https://ctftime.org/task/7458
Created python-gnupg tracking bugs for this issue: Affects: epel-6 [bug 1670367] Affects: epel-7 [bug 1670368] Affects: fedora-all [bug 1670366]
Mitigation: Filter out newlines from passphrases before passing them to python-gnupg.
Statement: The issue affects the versions of python-gnupg shipped with Red Hat Update Infrastructure 3, however the vulnerable functions are never used by the product. The issue affects the versions of python-gnupg shipped with Red Hat Satellite 6, however the vulnerable functions are never used by the product.
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2019-6690