Security Advisory

CVE-2022-4603: ppp pppdump Array Index (Disputed)

Last updated:
  • CVE-2022-4603

CVE-2022-4603 is a disputed missing index check in pppdump, the ppp project's offline tool for reading pppd record files, fixed in ppp 2.5.0. The record itself doubts the bug is real and notes pppdump is never used to set up a PPP connection or run automatically. NVD scores it 6.5, VulDB 4.3, and Debian rates it unimportant.

Vulnerability summary

CVSS base score

6.5

Medium severity

EPSS score (FIRST)

0.9%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2022-4603 · Source: NVD

Affected components

ComponentCPEVersion range
ppp (pppdump offline record-file decoder)cpe:2.3:a:samba:ppp:*:*:*:*:*:linux:*:*Before 2.5.0 (NVD, Linux and Solaris CPEs); fixed by commit a75fb7b1 of 2022-08-04, first release 2.5.0 (2023-04-04)
Debian ppp packagepkg:deb/debian/pppunstable fixed in 2.5.0-1+2 (urgency unimportant); trixie 2.5.2-1+1 and forky/sid 2.5.5-1+1 fixed; bookworm 2.4.9-1+1.1 listed vulnerable, unimportant, 'No security impact' (Debian security tracker, as of 2026-11-20)
OpenWrt package/network/services/ppp (pppdump subpackage)—pppdump is a separate package; openwrt-23.05 builds a 2.4.9 snapshot of 2021-01-04 (before the fix); openwrt-24.10 2.5.1, openwrt-25.12 2.5.2, main 2.5.5; all four branches remove pppd's record option (401-no_record_file.patch), as of 2026-11-20
Buildroot package/pppd—2023.02.x builds 2.4.9 and installs pppdump to /usr/sbin with no pppdump patch; 2.5.0 from commit 0c15169f (2023-09-29), first in Buildroot 2023.11; master builds 2.5.5 (as of 2026-11-20)

What does this mean for affected devices?

CVE-2022-4603 is a missing array-index check in pppdump, the offline tool in the ppp project that "converts the files written using the record option of pppd into a human-readable format" (pppdump manual). The CVE record, filed by VulDB as CNA on 2022-12-18 and tagged "disputed", says the function dumpppp in the pppdump tool's source lets spkt.buf/rpkt.buf be written without index validation, and adds two caveats: "The real existence of this vulnerability is still doubted at the moment", and "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" (NVD, CVE record).

What does the dispute mean in practice?

The fix came before the CVE. Paul Mackerras's commit a75fb7b1 of 2022-08-04, "pppdump: Avoid out-of-range access to packet buffer", checks pkt->cnt against the buffer size before storing a byte and prints "over-long packet truncated" for oversized packets. The commit message calls it "a potential vulnerability" and states that pppdump "is not used in the normal process of setting up a PPP connection, is not installed setuid-root, and is not invoked automatically in any scenario that I am aware of." To reach the bug, someone has to feed a crafted record file to a person or script that runs pppdump on it. The PPP link, pppd and its authentication code are not involved.

How severe is CVE-2022-4603?

NVD's Primary score is CVSS v3.1 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H). VulDB, the CNA, scores it 4.3 (CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L). Both use CWE-119; VulDB's entry narrows it to CWE-129, improper validation of array index. Debian rates it unimportant with the note "No security impact" (Debian security tracker). For a firmware review, the NVD number overstates the risk of a tool that only parses files on demand.

Which firmware and builds carry it?

NVD's CPE is cpe:2.3:a:samba:ppp for Linux and Solaris, versions before 2.5.0. ppp 2.5.0, released 2023-04-04, is the first release with the fix. No device vendor, CERT or CISA advisory names products for this CVE as of 2026-11-20. Downstream:

  • Debian fixed unstable in 2.5.0-1+2; trixie (2.5.2-1+1) and forky/sid (2.5.5-1+1) are fixed, and bookworm's 2.4.9-1+1.1 is listed as vulnerable with urgency unimportant.
  • OpenWrt builds pppdump as its own package ("Read PPP record file") in the ppp Makefile, so it is only present when selected. openwrt-23.05 builds a 2.4.9 snapshot of 2021-01-04, which predates the fix; openwrt-24.10 (2.5.1), openwrt-25.12 (2.5.2) and main (2.5.5) are past it. Every branch also carries 401-no_record_file.patch, which removes pppd's record option because "there is not enough space to record PPP session information", so an OpenWrt device does not produce the files pppdump reads.
  • Buildroot's package/pppd on the 2023.02.x branch builds 2.4.9 and installs pppdump to /usr/sbin alongside pppd with no pppdump patch. The bump to 2.5.0 (2023-09-29) first shipped in Buildroot 2023.11. Buildroot declares the CPE point-to-point_protocol_project:point-to-point_protocol, not NVD's samba:ppp, so CPE matching alone can miss this record.

How do you fix CVE-2022-4603?

Build ppp 2.5.0 or later, or apply commit a75fb7b1 to an older tree. Simpler still on a device: do not ship pppdump at all. It is a desktop-side analysis tool, so drop the OpenWrt pppdump package or delete /usr/sbin/pppdump in a Buildroot post-build script. Our pppd and PPP daemon guide covers the pppd flaws that do matter on routers and gateways, led by the EAP overflow CVE-2020-8597, and explains why this one is usually recorded as not reachable.

Is CVE-2022-4603 exploited?

It is not in the CISA KEV catalog as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries). FIRST EPSS gives it 0.00891, the 60.2nd percentile, in the 2026-11-19 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • NVD (read 2026-11-20): status Modified; published 2022-12-18T11:15:11.077; NVD Primary CVSS v3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H; VulDB Secondary 4.3 CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L; CWE-119 (both); CPE cpe:2.3:a:samba:ppp (linux, solaris) versionEndExcluding 2.5.0; description states existence is doubted and pppdump is not used to set up a PPP connection. — NVD
  • CVE record (read 2026-11-20): CNA VulDB, published 2022-12-18, tag 'disputed', title 'ppp pppdump pppdump.c dumpppp array index', problem type CWE-119 -> CWE-129, CNA CVSS v3.1 4.3. — CVE.org
  • ppp-project/ppp commit a75fb7b1 (Paul Mackerras, 2022-08-04), read 2026-11-20: 'pppdump: Avoid out-of-range access to packet buffer'; adds bounds check on pkt->cnt in dumpppp(); message says pppdump is not used in setting up a PPP connection, not setuid-root, not invoked automatically. Commit is after tag ppp-2.4.9 and contained in tag ppp-2.5.0; GitHub release 'PPP version 2.5.0' published 2023-04-04. pppdump.8 describes it as converting files written with pppd's record option. — ppp project (GitHub)
  • Debian security tracker (read 2026-11-20): ppp unstable fixed in 2.5.0-1+2, urgency unimportant; experimental 2.5.0-1+1; bookworm 2.4.9-1+1.1 vulnerable; trixie 2.5.2-1+1 and forky/sid 2.5.5-1+1 fixed; note 'No security impact'. — Debian
  • OpenWrt package/network/services/ppp Makefile (read 2026-11-20): main PKG_VERSION 2.5.5, openwrt-25.12 2.5.2, openwrt-24.10 2.5.1, openwrt-23.05 2.4.9 snapshot PKG_SOURCE_DATE 2021-01-04 (source 4fb31905); each defines a separate pppdump package 'Read PPP record file' installing /usr/sbin/pppdump; the patch 401-no_record_file.patch ('pppd: Remove the "record" option') present on all four branches. — OpenWrt
  • Buildroot package/pppd (read 2026-11-20): 2023.02.x PPPD_VERSION 2.4.9, PPPD_TARGET_BINS = chat pppd pppdump pppstats, patches 0001 and 0002 are build fixes only; commit 0c15169f 'package/pppd: bump version to 2.5.0' (2023-09-29); tag 2023.08 has 2.4.9, tag 2023.11 has 2.5.0; master 2.5.5; CPE vendor point-to-point_protocol_project. — Buildroot
  • Not in the CISA KEV catalog, version 2026.11.18 (1,786 entries), checked 2026-11-20. — CISA KEV
  • EPSS 0.00891, percentile 0.60152, dataset 2026-11-19, read 2026-11-20. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. ppp-project/ppp commit a75fb7b1: pppdump: Avoid out-of-range access to packet buffer
  3. ppp-project/ppp release: PPP version 2.5.0
  4. ppp-project/ppp pppdump(8) manual page
  5. Debian security tracker: CVE-2022-4603
  6. OpenWrt ppp package Makefile (main)
  7. OpenWrt ppp package (openwrt-23.05): 401-no_record_file.patch
  8. Buildroot commit 0c15169f: package/pppd: bump version to 2.5.0
  9. Buildroot package/pppd (2023.02.x)
  10. CVE.org record CVE-2022-4603 (CNA: VulDB, disputed)
  11. CISA KEV
  12. FIRST EPSS

Frequently asked questions

Is CVE-2022-4603 a real vulnerability?

It is disputed. The upstream commit fixes a genuine missing bounds check in pppdump, but the CVE record says the real existence of the vulnerability is doubted, and the maintainer notes pppdump is not used to set up connections, is not setuid-root and is never run automatically. Debian rates it unimportant with no security impact.

Does CVE-2022-4603 affect pppd PPP connections?

No. The flaw is only in pppdump, a separate program that decodes files written by pppd's record option. pppd, its authentication code and the PPP link itself do not run pppdump.

Which ppp version fixes CVE-2022-4603?

ppp 2.5.0, released 2023-04-04, is the first release with commit a75fb7b1. Debian ships the fix from 2.5.0-1+2 in unstable and in trixie; Buildroot from 2023.11; OpenWrt from the openwrt-24.10 branch (ppp 2.5.1).

What should a firmware team do about it?

Usually remove pppdump rather than patch it, since devices rarely need an offline record-file decoder. On OpenWrt it is a separate package that can be left unselected; on Buildroot 2023.02.x it is installed with pppd and can be deleted in a post-build script. Then record the finding as not reachable.