[security fix] GnuPG 2.2.23 released

Hello dear admins and developers
How long will it take until this vulnerability is closed by an update/batch from GnuPG to Manjaro?
Here is an excerpt from the announcement of the GnuPG development team (unfortunately I cannot post any links)


Hello!

We are pleased to announce the availability of a new GnuPG release:
version 2.2.23. This version fixes a critical security bug in
versions 2.2.21 and 2.2.22.

Impact

These versions are affected:

  • GnuPG 2.2.21 (released 2020-07-09)
  • GnuPG 2.2.22 (released 2020-08-27)
  • Gpg4win 3.1.12 (released 2020-07-24)

All other versions are not affected.

Importing an OpenPGP key having a preference list for AEAD algorithms
will lead to an array overflow and thus often to a crash or other
undefined behaviour.

Importing an arbitrary key can often easily be triggered by an attacker
and thus triggering this bug. Exploiting the bug aside from crashes is
not trivial but likely possible for a dedicated attacker. The major
hurdle for an attacker is that only every second byte is under their
control with every first byte having a fixed value of 0x04.

Software distribution verification should not be affected by this bug
because such a system uses a curated list of keys.

A CVE-id has not yet been assigned. We track this bug at

Solution

If GnuPG version 2.2.21 or 2.2.22 is in use please update ASAP to
version 2.2.23.

If you are using an older version or a beta of version 2.3 no immediate
action is required.

If you are using Gpg4win 3.1.12 or GnuPG VS-Desktop 3.1.12 you may
either wait for a fixed release which we will provide very soon or
install GnuPG version 2.2.23 on top.

Hello and thanks for reporting and for your concerns.
using Manjaro - Branch Compare
You will see that gnupg 2.2.23 is already in unstable and testing branches.

Packages Stable Testing Unstable Repository
gnupg 2.2.21-1 2.2.23-1 2.2.23-1 core

@philm - can we do something about this to have it quicker delivered to stable branch too? Thanks!

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.