# CVE-2020-6923: HP Linux Imaging and Printing Software - Potential Memory Buffer Overflow

> A memory buffer overflow in HP Linux Imaging and Printing software could allow attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Dec 2024
- **Updated:** 20 Dec 2024
- **Also known as:** DEBIAN-CVE-2020-6923, GHSA-v356-2ghm-7mwq, OESA-2025-1010, OESA-2025-1011, OESA-2025-1012, OESA-2025-1013, SUSE-RU-2025:0270-1, SUSE-RU-2025:0272-1, SUSE-SU-2025:0290-1, UBUNTU-CVE-2020-6923, USN-7202-1, openSUSE-SU-2025:14655-1

## What is CVE-2020-6923?

CVE-2020-6923 is a medium-severity memory corruption vulnerability in HP Linux Imaging and Printing Software, published on 19 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The HP Linux Imaging and Printing (HPLIP) software may potentially be affected by memory buffer overflow.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-6923?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hplip` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 3.24.4-150600.4.6.1 |
| `hplip` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 3.24.4-150600.4.6.1 |
| `hplip` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 3.24.4-3.5.1 |
| `hplip` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.24.4-3.5.1 |
| `hplip` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Manager Proxy 4.3 | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | SUSE:Manager Server 4.3 | All versions | 3.24.4-150400.3.17.1 |
| `hplip` | openSUSE:Leap 15.6 | All versions | 3.24.4-150600.4.6.1 |
| `hplip` | openSUSE:Tumbleweed | All versions | 3.24.4-4.1 |

## How do I fix CVE-2020-6923?

Apply the vendor's patch.

## Is CVE-2020-6923 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6923 and fix it if it is affected.

What it is: CVE-2020-6923 is a medium-severity memory corruption vulnerability in HP Linux Imaging and Printing Software, published on 19 Dec 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-6923 in the wild and no public exploit code.

Affected product: HP Linux Imaging and Printing Software. 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-2020-6923/ (Markdown: https://insights.sbomify.com/CVE-2020-6923/index.md)
```

## Sources

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

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