RCE in Gnupg

(lists.gnupg.org)

197 points | by gdgghhhhh 12 hours ago

13 comments

  • uptrails 9 hours ago

    Reportedly fixed by Red Hat 5 years ago based on the output from conventional tools, but missed by upstream: https://gitlab.com/redhat/centos-stream/rpms/gpgme/-/blob/c9...

    • gdgghhhhh 8 hours ago
      • sandos 1 hour ago

        How is this even possible?

        "when it was noticed by a Coverity scan:"

        It was found by static analysis FIVE years ago, but never re-found? That is really odd. I thought people were running every kind of commercial scanning tool on OSS for free most of the time.

        • hannob 21 minutes ago

          Who are those people you thought would do that?

          Sure, you can get coverity scans for free for open source tools. Most open source maintainers I know aren't eager to hear ideas how they can have more work maintaining their software.

        • c-hendricks 6 hours ago

          Hurray for endless distro forks

          • christophilus 6 hours ago

            Rh is kind of the canonical distro, though, as much as there is such a thing. I’m surprised this was never upstreamed.

            • gpvos 1 hour ago

              Used to be long ago. Maybe still is somewhat for business use. Debian or Ubuntu has been the most standard distro for many years now.

              • cozzyd 1 hour ago

                Depends on your circles...

              • BadBadJellyBean 2 hours ago

                RH has a lot of sway but calling it canonical would be a step too far in my opinion.

                • cowlevel 1 hour ago

                  Debian is the canonical distro.

                  Ubuntu is the Canonical distro, but that's unrelated.

                  • creatonez 17 minutes ago

                    Debian is vastly further from upstream than Red Hat.

                  • throooooo 5 hours ago

                    No Canonical makes Ubuntu. Jokes aside, Ubuntu and Debian are the most used distros by far.

                    • eddythompson80 2 hours ago

                      In my personal experience, I think both of you are right in different bubbles (for lack of a better word). If you worked in commercial unix-like tech systems since the early 2000s (meaning your company/business was tech focused), you would consider RH to be the canonical distro. There is a reason all the newer distros marketed towards commercial use (Alma, Rocky, Cent, Core, Amazon, Azure) are all Fedora/RH derivatives.

                      If you have been mainly OSS or used unix-system in a non-tech business, then you would consider Debian/Ubuntu to be the more canonical distros.

                      • cozzyd 1 hour ago

                        In HEP and academic cluster environments EL is standard. I only use Debian on embedded Linux.

                      • nullpoint420 3 hours ago

                        It's unfortunate because they're definitely not the best, even at the reasons Ubuntu is often cited for being "better."

                        IMO, RH is just better at security, integration, and much much more.

                        • johnsonjo 3 hours ago

                          Yeah I use Ubuntu and Fedora and the only thing I don't like about my Fedora desktop is that more desktop software is only available for Ubuntu/Debian rather than Fedora. Probably only simply because Ubuntu is more popular. (I have used alien in the past to some success in this regard to get software running on Fedora that was only built for Ubuntu.)

                          More on alien:

                          > alien is a program that converts between Red Hat rpm, Debian deb, Stampede slp, Slackware tgz, and Solaris pkg file formats. If you want to use a package from another linux distribution than the one you have installed on your system, you can use alien to convert it to your preferred package format and install it. It also supports LSB packages. [1]

                          [1]: (https://manpages.ubuntu.com/manpages/bionic/man1/alien.1p.ht...)

                • miduil 10 hours ago

                         This vulnerability was discovered by Johan Carlsson and we were informed by GitLab on 2026-11-12.
                         Initially we set 2026-11-25 for a coordinated disclosure;
                         due to the new Ruby2Shell bug GitLab had to update earlier
                         and thus we also disclosed the GPGME bug on 2026-11-20.
                  
                  I guess pretty important for GitLab since it supports signed commits, code execution in that path is pretty bad.

                  You can find the GitLab Omnibus related patch here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/commit/279ac3...

                  • dehrmann 2 hours ago

                    It's becoming clear that humans have no business writing C/C++ without Rust-level tooling around it to prevent these things.

                    • mik1998 8 hours ago

                      It's a double free bug, not an RCE chain. Are these vulnerability reports intentionally overstated?

                      • cowlevel 1 hour ago

                        AI is doing quite well at automating the escalation of small memory bugs (which can usually theoretically cause RCEs) into actual RCE exploits. This bug has a similar nature to php2shell.

                        • InsidiousWombat 6 hours ago

                          Yes, the actual post just implies possibility

                          > Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.

                          • mhluongo 5 hours ago

                            Today's LLMs can often escalate to RCE, so it makes sense to assume the worst.

                            • slim 2 hours ago

                              it does not make sense to say RCE for something that does not have an open port on the system

                              • rubendev 1 hour ago

                                If someone opens an encrypted email that came from an attacker using GnuPG and code is executed on his machine as a result, that is still remote code execution.

                                • dwattttt 1 hour ago

                                  What is not "remote" code execution under this definition?

                                  • catlifeonmars 55 minutes ago

                                    Have you ever heard of IP over Avian Carrier? It might help expand your definition of “remote”.

                                    In all seriousness, “remote” in this case means attacker controlled.

                                    • dwattttt 32 minutes ago

                                      Are you suggesting the existence of exploits outside of the definition of "attacker controlled"?

                                      If not, and all exploits are attacker controlled, it sounds like all exploits are RCE.

                                      EDIT I guess I have to weaken the last condition since we haven't proved all exploits are "code execution", but we have at least proved all exploits are "remote".

                              • gertop 4 hours ago

                                It makes sense to assume the worst, then try to achieve it. And only if you achieve it so you tag it as such. You can't announce vulnerabilities to the world based on vibes of what it might do....

                                "Yeah this is a classic double free. We can't think of a way to transform it into a RCE or something like that, we've also failed at having LLMs do it so far. but in the current climate it could happen so we humbly ask the tag of most dangerous vulnerability please. Not just this disclaimer. We want 9.9 CVE that says RCE!!"

                                This is ridiculous.

                              • gdgghhhhh 8 hours ago

                                Sending somebody a signed message and trigger a double free is a prime example for RCE

                                • kuroguro 8 hours ago

                                  RCE might be possible, you still need to overlay something useful in the freed memory and bypass ASLR.

                                  • Deeg9rie9usi 7 hours ago

                                    The mail says "Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.". They didn't write this just for fun. gnupg usually downplays security issues.

                                    • kuroguro 7 hours ago

                                      I'd say that is as accurate as they can be. Since it's a library and it's a heap bug they have no idea how a particular application will be affected.

                                      It's still a critical bug, just would not call it a prime example of rce.

                                      • wavemode 6 hours ago

                                        I mean, the blame is moreso on the title of this HackerNews submission. "RCE can't be ruled out" is not equivalent to "RCE in Gnupg"

                                        • Sopel 7 hours ago

                                          it can't be ruled out that an RCE exists in other parts of this software either

                                      • dboreham 4 hours ago

                                        "overlay something useful in the freed memory and bypass ASLR"

                                        I thought we reached the point a few years ago where the assumed probability this can be done is 100% ?

                                      • gsich 8 hours ago

                                        poc needed.

                                        • Deeg9rie9usi 8 hours ago

                                          IMHO, these days any kind of UB has to be considered exploitable by an LLM. The times of debating whether something is exploitable or not are over.

                                          • Deeg9rie9usi 6 hours ago

                                            It's interesting to see how polarizing this comment is, it's being upvoted and downvoted in waves.

                                            • gsich 7 hours ago

                                              We are having this debate right now. So it's far from over. Without PoC it's unclear if it's RCE or just overhyped bullshit. See PHP or Nginx "RCE" which required specific crafted settings for it to even work. A video is not a "PoC".

                                              If you believe an LLM can generate an exploit for this - feel free to post one.

                                              • o_-_o 7 hours ago

                                                I agree PoC's should be a requirement for all this exploits.

                                                • InsidiousWombat 6 hours ago

                                                  at the very least should be criteria for assigning "high", CVE spam is annoying enough as it is

                                                • pixl97 4 hours ago

                                                  Na, for years I've been seeing crap like this "well there is no exploit" and then a year later one is found.

                                                  Quit writing memory free errors in software. Prove your software is safe, not prove that it's not exploitable.

                                                  • gsich 2 hours ago

                                                    A year later you hopefully have updated the software, no loss there.

                                                    • pixl97 34 minutes ago

                                                      It's more of a "made public" a year later, you have no idea if anyone exploited it in between.

                                                      At first I thought the whole Linux everything is a CVE was kind of annoying, but over time, especially with automated exploit finding it really has shown to be in front of what was about to happen.

                                        • wannabe44 3 hours ago

                                              All software using a GPGME version prior to 2.3.0 either as shared
                                          libary, DLL, or statically linked is affected. Examples of software using GPGME are

                                             - Gpg4win
                                             - GnuPG Desktop
                                             - GnuPG VS-Desktop
                                             - Most mail clients
                                             - Many XMPP clients
                                             - Samba
                                             - Flatpack
                                          
                                          I assume this is in "gpgme" and doesn't affect apt etc? Can someone confirm?
                                          • usr1106 8 hours ago

                                            What are practical attack vectors for Linux workstations and servers?

                                            The masses of internet users don't know what GPG is. I'd caim the majority of software developers don't have a GPG key and never explicitly verify any signature.

                                            But packages of many distros are verified using GPG. Is the vulnerable component involved or not?

                                            • kodoman 6 hours ago

                                              > But packages of many distros are verified using GPG. Is the vulnerable component involved or not?

                                              Debian uses it last time I was on a Debian system And I think all Debian based distros that don't modify apt will essentially use GPG to verify the packages as well.

                                              I think it's one of the those programs that pop up in a lot of different things. Personally I use it a fair amount and even use the Symmetric encryption features for some files and for personal password management.

                                              I do think developer are moving away from it thought I agree (and for various reasons that are good).

                                              • lazka 7 hours ago

                                                Arch Linux uses gpgme to verify downloaded packages (and optionally, package databases) for example.

                                                • firesteelrain 5 hours ago

                                                  It’s used a lot in commercial for code signing. We use it with Thales HSMs (there are other things in the middle)

                                                  • usr1106 5 hours ago

                                                    Are you sure? (I am not) The announcement says gpgme. Is that the same thing used for basic signatures?

                                                  • OJFord 7 hours ago

                                                    Potentially package update/installation? A lot of people use gpg without knowing it.

                                                    It's specifically in 'GPGME' though, so more limited scope I think.

                                                    • capitol_ 7 hours ago

                                                      A lot of those places have switched out the gnupg PGP implementation with sequoia-openpgp.

                                                      • usr1106 5 hours ago

                                                        Interesting. Can you give examples. The only places I have met sequoia were conference talks by their maintainer, probably founder.

                                                      • usr1106 7 hours ago

                                                        That was my question. Where is gpgme used? Any "unexpected" places?

                                                      • gdgghhhhh 8 hours ago

                                                        PGP mail?

                                                        • Geezus_42 8 hours ago

                                                          Which almost no one uses.

                                                          • gdgghhhhh 8 hours ago

                                                            Wrong bubble ;-)

                                                            • Geezus_42 7 hours ago

                                                              If only people in a certain bubble use it, then almost no one actually uses it.

                                                              • kodoman 6 hours ago

                                                                > no one actually uses it.

                                                                A lot of people use it especially certain high value targets on darknet drug markets who might miss this.

                                                                A lot of projects do still use it for signing projects though many have opted for simpler solutions (or unfortunately no signing).

                                                                I think Debian still uses it (not sure about ubuntu) in apt.

                                                                • Geezus_42 6 hours ago

                                                                  Darknet drug dealers are still an extreme minority of people. You still have not negated my statement.

                                                                  Sure, GPG gets used for signing packages and that COULD potentially lead to a supply chain attack IF this is not quickly patched.

                                                      • tombardier 4 hours ago

                                                        "We are pleased to announce..."

                                                        • gpvos 1 hour ago

                                                          Bugfixes are good.

                                                        • usr1106 7 hours ago

                                                          Editorialized submission title to be better bait.

                                                          The correct title is: GnuPG Security Advisory for GPGME

                                                          • g-b-r 6 hours ago

                                                            Which wouldn't tell us anything before checking the link

                                                            • fn-mote 6 hours ago

                                                              The current title is "RCE in Gnupg". A more appropriate title would be "Double free produces posible RCE in GnuPG". The non-editorialized title would also be better because it does not claim there is an RCE that is not known to exist.

                                                              "Probable RCE in GnuPG clients" would be appropriate.

                                                              When someone posts a Claude POC, then the situation is different.

                                                              • msm_ 1 hour ago

                                                                >Double free produces posible RCE in GnuPG

                                                                Not even that, just "double free" would be a fair title. Every double free is a possible RCE using this logic. For tens of years we had "double free" vulnerabilities. Calling each and every of them "RCE" makes that word meaningless.

                                                                • g-b-r 6 hours ago

                                                                  Alright, possible RCE would be fair

                                                            • fock 6 hours ago

                                                              so essentially look at the key before? (and hope your program does not have another RCE...)

                                                              • Velocifyer 7 hours ago

                                                                This is a reminder that Seqouia-PGP exists, and its 'sq' CLI is way more intuitive.

                                                                • mmsc 8 hours ago

                                                                  The vulnerability is in GpgME (the library), not GnuTLS (the library).

                                                                  • legsrunny 9 hours ago

                                                                    more or less than 0 impacted systems?

                                                                    • IshKebab 7 hours ago

                                                                      Luckily nobody uses it!