This is CVE-2018-12020. Probably affects all versions.
Description
Description
Revisions and Commits
Revisions and Commits
rG GnuPG | |||
rG2326851c6079 gpg: Sanitize diagnostic with the original file name. | |||
rG210e402acd3e gpg: Sanitize diagnostic with the original file name. | |||
rG13f135c7a252 gpg: Sanitize diagnostic with the original file name. |
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | • werner | T4012 Diagnostic is shown with the original filename not being sanitized. | ||
Resolved | • werner | T4015 Release 1.4.23 |
Event Timeline
Comment Actions
Fixed in 1.4, 2.2 and master. New releases will be done soon. Note that there is no need for a new gpg4win release because GPGME is not affected.
Comment Actions
@dkg can you please take this up with Debian and other distros? See the commit for a brief description.
Comment Actions
[Better use the gnupg tag. Specific versions end up on the workboard and there may only be one.]
Comment Actions
Unfortunately 2.2.8 does not build with older libgpg-error versions. Commit rG18274db32b5dea7fe8db67043a787578c975de4d should fix this.
Comment Actions
Timeline:
Request for key | Thu, 7 Jun 2018 11:48 +0200 |
Reply from us | Thu, 7 Jun 2018 19:05 +0200 |
Report date | Fri, 8 Jun 2018 09:14 +0200 |
Fix committed | Fri, 8 Jun 2018 11:09 +0200 |
Announcement and release | Fri, 8 Jun 2018 15:41 +0200 |