# CVE-2022-4603: ppp pppdump pppdump.c dumpppp array index

> Improper array index validation in pppdump may cause memory corruption, though exploitation is unlikely as the tool is not used in standard PPP connections.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-4603, AZL-11860, AZL-36979, CLSA-2026-1785768873, CLSA-2026-1786622639, DEBIAN-CVE-2022-4603, GHSA-82mr-xx64-4rjv, OESA-2023-1015, SUSE-SU-2023:4961-1, SUSE-SU-2023:4965-1, SUSE-SU-2024:2380-1, openSUSE-SU-2024:13529-1

## What is CVE-2022-4603?

CVE-2022-4603 is a medium-severity memory corruption vulnerability in unspecified ppp, published on 18 Dec 2022. 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

A vulnerability classified as problematic has been found in ppp. Affected is the function dumpppp of the file pppdump/pppdump.c of the component pppdump. The manipulation of the argument spkt.buf/rpkt.buf leads to improper validation of array index. The real existence of this vulnerability is still doubted at the moment. The name of the patch is a75fb7b198eed50d769c80c36629f38346882cbf. It is recommended to apply a patch to fix this issue. VDB-216198 is the identifier assigned to this vulnerability. NOTE: pppdump is not used in normal process of setting up a PPP connection, is not installed setuid-root, and is not invoked automatically in any scenario.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2022-4603?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ppp` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | SUSE:Linux Enterprise Real Time 15 SP4 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 2.4.7-4.6.1 |
| `ppp` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 2.4.7-4.6.1 |
| `ppp` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.4.7-4.6.1 |
| `ppp` | openSUSE:Leap 15.4 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | openSUSE:Leap 15.5 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | openSUSE:Leap Micro 5.3 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | openSUSE:Leap Micro 5.4 | All versions | 2.4.7-150000.5.13.1 |
| `ppp` | openSUSE:Tumbleweed | All versions | 2.5.0-1.1 |

Products: Samba Ppp.

## How do I fix CVE-2022-4603?

Apply the vendor's patch.

## Is CVE-2022-4603 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4603 and fix it if it is affected.

What it is: CVE-2022-4603 is a medium-severity memory corruption vulnerability in unspecified ppp, published on 18 Dec 2022. 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-2022-4603 in the wild and no public exploit code.

Affected product: unspecified ppp. 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-4603/ (Markdown: https://insights.sbomify.com/CVE-2022-4603/index.md)
```

## Sources

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

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