# CVE-2022-34903: Other in n/a > Attackers with partial key access can forge signatures via status line injection in GnuPG under specific GPGME conditions. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Jul 2022 - **Updated:** 3 Aug 2024 - **Also known as:** ALPINE-CVE-2022-34903, ALSA-2022:6463, ALSA-2022:6602, AZL-10074, CLEANSTART-2026-RL04629, CLSA-2022-1657815972, CLSA-2023-1687469258, DEBIAN-CVE-2022-34903, DSA-5174-1, GHSA-356p-pg27-x2cf, JLSEC-2025-92, MGASA-2022-0259, MINI-8vj2-74jc-7c9m, OESA-2022-1847, RHSA-2022:6463, RHSA-2022:6602, RLSA-2022:6463, RLSA-2022:6602, SUSE-SU-2022:2529-1, SUSE-SU-2022:2546-1, SUSE-SU-2022:3144-1, UBUNTU-CVE-2022-34903, USN-5503-1, USN-5503-2, openSUSE-SU-2022:2546-1, openSUSE-SU-2024:12215-1 ## What is CVE-2022-34903? CVE-2022-34903 is a medium-severity vulnerability in Debian Debian Linux, published on 1 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description GnuPG through 2.3.6, in unusual situations where an attacker possesses any secret-key information from a victim's keyring and other constraints (e.g., use of GPGME) are met, allows signature forgery via injection into the status line. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2022-34903? It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gnupg2` | AlmaLinux:8 | All versions | 2.2.20-3.el8_6 | | `gnupg2-smime` | AlmaLinux:8 | All versions | 2.2.20-3.el8_6 | | `gnupg2` | AlmaLinux:9 | All versions | 2.3.3-2.el9_0 | | `gnupg2-smime` | AlmaLinux:9 | All versions | 2.3.3-2.el9_0 | | `gnupg2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.2.20-3.el8_6 | | `gnupg2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.2.20-3.el8_6 | | `gnupg2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.2.20-3.el8_6 | | `gnupg2-smime` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.2.20-3.el8_6 | | `gnupg2-smime-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.2.20-3.el8_6 | | `gnupg2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.3.3-2.el9_0 | | `gnupg2-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.3.3-2.el9_0 | | `gnupg2-smime` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.3.3-2.el9_0 | | `gnupg2-smime-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.3.3-2.el9_0 | | `gnupg2` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.3.3-2.el9_0 | | `gnupg2-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.3.3-2.el9_0 | | `gnupg2-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.3.3-2.el9_0 | | `gnupg2-smime-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.3.3-2.el9_0 | | `gnupg2` | Rocky Linux:8 | All versions | 0:2.2.20-3.el8_6 | | `gnupg2` | Rocky Linux:9 | All versions | 0:2.3.3-2.el9_0 | | `gpg2` | SUSE:Enterprise Storage 6 | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Enterprise Storage 7 | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise Micro 5.1 | All versions | 2.2.27-150300.3.5.1 | | `gpg2` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.2.27-150300.3.5.1 | | `gpg2` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 2.2.27-150300.3.5.1 | | `gpg2` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 2.2.27-150300.3.5.1 | | `gpg2` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 2.0.24-9.11.1 | | `gpg2` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 2.0.24-9.11.1 | | `gpg2` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 2.0.24-9.11.1 | | `gpg2` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.0.24-9.11.1 | | `gpg2` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise Server 15 SP2-BCL | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.2.5-150000.4.22.1 | | `gpg2` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 2.2.5-150000.4.22.1 | Products: Debian Debian Linux, Fedoraproject Fedora, Gnupg Gnupg, Netapp Active Iq Unified Manager, Netapp Ontap Select Deploy Administration Utility. ## How do I fix CVE-2022-34903? Upgrade to a fixed version. ## Is CVE-2022-34903 being exploited? There is no known exploitation of CVE-2022-34903 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-34903 and fix it if it is affected. What it is: CVE-2022-34903 is a medium-severity vulnerability in Debian Debian Linux, published on 1 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-34903 in the wild and no public exploit code. Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-34903/ (Markdown: https://insights.sbomify.com/CVE-2022-34903/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-34903 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-34903 - OSV: https://osv.dev/vulnerability/CVE-2022-34903 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-34903/ Summaries are generated and may contain mistakes; the official description above is the record.