[3.6] gnupg: filename sanitization problem (CVE-2018-12020)
GnuPG before version 2.2.8 does not properly sanitize original filenames
of signed or encrypted messages allowing for the insertion of line feeds
and other control characters.
An attacker could exploit this by injecting such characters to craft
status messages and fake the validity of signatures.
References:
https://lists.gnupg.org/pipermail/gnupg-announce/2018q2/000425.html
Patches:
https://dev.gnupg.org/rG2326851c60793653069494379b16d84e4c10a0ac
https://dev.gnupg.org/rG210e402acd3e284b32db1901e43bf1470e659e49
https://dev.gnupg.org/rG13f135c7a252cc46cff96e75968d92b6dc8dce1b
(from redmine: issue id 8995, created on 2018-06-13, closed on 2018-06-14)
- Relations:
- copied_to #8993 (closed)
- parent #8993 (closed)
- Changesets:
- Revision 0b8633cb on 2018-06-13T13:42:40Z:
main/gnupg: security fix (CVE-2018-12020)
Fixes #8995