# CVE-2005-2023: The send_pinentry_environment function in asshelp.c in gpg2 on SUSE Linux 9.3 does not properly handle certain options, which can prevent pi


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2023, GHSA-5phw-pq6g-29m4

## What is CVE-2005-2023?

CVE-2005-2023 is a critical vulnerability in Suse Suse Linux, published on 21 Jun 2005. 

### Official description

The send_pinentry_environment function in asshelp.c in gpg2 on SUSE Linux 9.3 does not properly handle certain options, which can prevent pinentry from being found and causes S/MIME signing to fail.

## Which versions are affected by CVE-2005-2023?

It affects 1 product.


Products: Suse Suse Linux.

## How do I fix CVE-2005-2023?

Upgrade to a fixed version.

## Is CVE-2005-2023 being exploited?

There is no known exploitation of CVE-2005-2023 in the wild and no public exploit code.

## Other vulnerabilities in Suse Suse Linux

- [CVE-2007-0460](https://insights.sbomify.com/CVE-2007-0460/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-2004](https://insights.sbomify.com/CVE-2004-2004/): The Live CD in SUSE LINUX 9.1 Personal edition is configured without a password for root, which allows remote attackers to gain privileges via SSH. (critical 10.0)
- [CVE-2000-1040](https://insights.sbomify.com/CVE-2000-1040/): Denial of service in n/a (critical 10.0)
- [CVE-2000-1044](https://insights.sbomify.com/CVE-2000-1044/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-0800](https://insights.sbomify.com/CVE-2000-0800/): Privilege escalation in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2023 and fix it if it is affected.

What it is: CVE-2005-2023 is a critical vulnerability in Suse Suse Linux, published on 21 Jun 2005. 
Exploitation: There is no known exploitation of CVE-2005-2023 in the wild and no public exploit code.

Affected product: Suse Suse 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-2005-2023/ (Markdown: https://insights.sbomify.com/CVE-2005-2023/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-2023
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-2023
- OSV: https://osv.dev/vulnerability/CVE-2005-2023

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-2023/
Summaries are generated and may contain mistakes; the official description above is the record.