Security Advisory

CVE-2019-12111: MiniUPnPd PCP NULL Dereference

Last updated:
  • CVE-2019-12111

CVE-2019-12111 is a NULL pointer dereference (CWE-476) in copyIPv6IfDifferent() in the PCP server of MiniUPnPd through 2.1: a crafted Port Control Protocol request crashes the daemon, which stops UPnP and PCP port mapping on the router. NVD scores it 7.5. MiniUPnPd 2.2.0 is the first release with the fix.

Vulnerability summary

CVSS base score

7.5

High severity

EPSS score (FIRST)

3.4%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2019-12111 · Source: NVD

Affected components

ComponentCPEVersion range
MiniUPnPd (MiniUPnP IGD daemon)cpe:2.3:a:miniupnp_project:miniupnpd:*:*:*:*:*:*:*:*through 2.1 (NVD); fix dated 2018-12-18, first release 2.2.0 (2020/10/31)
OpenWrt packages feed: miniupnpdcpe:2.3:a:miniupnp_project:miniupnpd:*:*:*:*:*:*:*:*openwrt-18.06: 2.1 with a build patch only; openwrt-19.07: 2.2.0; master 2.3.11 (read 2026-11-18)
Debian miniupnpdcpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*fixed in 1.8.20140523-4+deb8u1 (jessie, DLA-1811-1) and 2.1-6 (unstable); stretch marked no-dsa (minor issue)

What does this mean for affected devices?

NVD's description: "A Denial Of Service vulnerability in MiniUPnP MiniUPnPd through 2.1 exists due to a NULL pointer dereference in copyIPv6IfDifferent in pcpserver.c." NVD's Primary score is CVSS v3.1 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with CVSS v2 5.0 and CWE-476. The CPE configuration covers MiniUPnPd through 2.1 under the vendor name miniupnp_project, plus Debian 8.0. The record was published on 2019-05-15 together with CVE-2019-12107 (NVD).

When does a device expose the PCP code?

PCP (Port Control Protocol) is the successor of NAT-PMP, and MiniUPnPd serves both on the same UDP sockets. In the 2.1 source from the MiniUPnP download page, genconfig.sh compiles PCP in by default, but the daemon opens the NAT-PMP/PCP sockets only when enable_natpmp=yes is set in miniupnpd.conf or it is started with -N; the sample configuration comments the option out and says "default is no". copyIPv6IfDifferent() is a two-line helper that calls memcpy() on its source argument when source and destination differ, with no NULL check. The Debian security tracker notes that the helper was introduced later but the NULL dereference on that argument existed before it, and it rates the issue minor for stretch. The fix in the MiniUPnP repository, dated 2018-12-18, adds the NULL check; 2.1 shipped on 2018/05/08 and 2.2.0 on 2020/10/31, per the project Changelog.

Which firmware carries it?

The OpenWrt packages feed packaged MiniUPnPd 2.1 on openwrt-18.06 with only a build patch, then 2.2.0 on openwrt-19.07, and builds 2.3.11 on master as of 2026-11-18. Debian fixed jessie's 1.8.20140523 package in DLA-1811-1. On a router image, check both the MiniUPnPd version and whether NAT-PMP/PCP is switched on in the shipped configuration; a 2.1 daemon with it off does not answer PCP. Our MiniUPnPd and UPnP firmware guide shows where the configuration sits on OpenWrt-based images.

How do you fix or mitigate it?

Upgrade to a current MiniUPnPd release, which also covers CVE-2019-12107 and the older CVE-2013-0229. Until then, leave enable_natpmp off unless clients need PCP or NAT-PMP, and make sure the NAT-PMP/PCP port, UDP 5351 in the MiniUPnPd source, does not answer on the WAN interface. The memory corruption fix guide covers NULL checks on parsed protocol fields.

CVE-2019-12111 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.03404, the 89th percentile, in the 2026-11-17 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: DoS in MiniUPnPd through 2.1 due to NULL pointer dereference in copyIPv6IfDifferent in pcpserver.c; Primary CVSS v3.1 7.5 A:H, v2 5.0; CWE-476; CPE cpe:2.3:a:miniupnp_project:miniupnpd through 2.1 and Debian 8.0; published 2019-05-15. — NVD
  • miniupnpd-2.1.tar.gz: copyIPv6IfDifferent() memcpy without NULL check; genconfig.sh defines ENABLE_PCP; NAT-PMP/PCP sockets opened only with ENABLENATPMPMASK (enable_natpmp=yes or -N); sample conf '# Enable NAT-PMP support (default is no)'. — MiniUPnP download page
  • MiniUPnP repository commit of 2018-12-18 'pcpserver.c: copyIPv6IfDifferent() check for NULL src argument', contained in release tag miniupnpd_2_2_0 and not in miniupnpd_2_1. — MiniUPnP project (GitHub)
  • MiniUPnPd Changelog: VERSION 2.1 released 2018/05/08; VERSION 2.2.0 released 2020/10/31. — MiniUPnP project (GitHub)
  • Debian security tracker: fixed jessie 1.8.20140523-4+deb8u1 (DLA-1811-1), unstable 2.1-6; stretch no-dsa (minor issue); helper introduced later but NULL dereference on the argument present before. — Debian security tracker
  • OpenWrt packages net/miniupnpd: 2.1 on openwrt-18.06, 2.2.0 on openwrt-19.07, 2.3.11 on master; read 2026-11-18. — OpenWrt packages
  • CVE-2019-12111 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.03404, percentile 0.89073, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. MiniUPnP project repository
  3. MiniUPnPd Changelog
  4. MiniUPnP project: release downloads
  5. OpenWrt packages: miniupnpd Makefile (openwrt-18.06)
  6. Debian security tracker
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Which MiniUPnPd versions are affected by CVE-2019-12111?

NVD lists MiniUPnPd through 2.1. The NULL check in copyIPv6IfDifferent() is dated 2018-12-18 in the project repository, and 2.2.0, released on 2020/10/31, is the first release that contains it (per NVD and the MiniUPnP project).

Is a router affected by CVE-2019-12111 if NAT-PMP and PCP are switched off?

In MiniUPnPd 2.1 the PCP code is compiled in by default, but the daemon opens its NAT-PMP/PCP sockets only when enable_natpmp=yes is configured or it runs with -N, and the sample configuration leaves that off. With PCP off, the crafted request has nothing to reach (per the MiniUPnPd 2.1 source).

What happens when CVE-2019-12111 is triggered?

The daemon dereferences a NULL pointer and crashes, which NVD rates as a high availability impact (7.5). While the daemon is down, the router answers no UPnP IGD or PCP port-mapping requests (per NVD and the MiniUPnPd 2.1 source).

Is CVE-2019-12111 in the CISA KEV catalog?

No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.03404, the 89th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).