CVE-2019-12312 json
In Libreswan 3.27 an assertion failure can lead to a pluto IKE daemon restart.
published 7y ago modified 4mo ago also EUVD-2019-3949
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
In Libreswan 3.27 an assertion failure can lead to a pluto IKE daemon restart. An attacker can trigger a NULL pointer dereference by initiating an IKEv2 IKE_SA_INIT exchange, followed by a bogus INFORMATIONAL exchange instead of the normallly expected IKE_AUTH exchange. This affects send_v2N_spi_response_from_state() in programs/pluto/ikev2_send.c that will then trigger a NULL pointer dereference leading to a restart of libreswan.
Patch / fix
- libreswan libreswan 3.28
- libreswan Debian 13, Debian 12 3.27-5
debian advisories DEBIAN-CVE-2019-12312
- libreswan RHEL 8 3.29-6.el8
red hat advisories RHSA-2019:3391
- libreswan Alpine 3.24, Alpine 3.23, Alpine 3.22 +11 more 3.28-r0
alpine advisories ALPINE-CVE-2019-12312
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2019-12312 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-12312 updated cvss 4.3
libreswan: null-pointer dereference by sending two IKEv2 packets
-
Red Hat Enterprise Linux AppStream (v. 8) libreswan 3.29-6.el8fixed: vendor fix RHSA-2019:3391
-
Red Hat Enterprise Linux 5 openswan Red Hat Enterprise Linux 6 openswan, libreswan Red Hat Enterprise Linux 7 libreswannot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.75% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- iwantacve.cn http://www.iwantacve.cn/index.php/archives/218/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
References
-
github.com
/libreswan/libreswan/compare/9b1394e...3897683
patch, third-party-advisory
-
iwantacve.cn
/index.php/archives/218/
exploit, third-party-advisory
-
github.com
/libreswan/libreswan/issues/246
third-party-advisory
- libreswan.org /security/CVE-2019-12312/CVE-2019-12312.txt
- libreswan.org /security/CVE-2019-12312/libreswan-3.27-CVE-2019-12312.patch
Sources
- CVE List CVE-2019-12312
- NVD CVE-2019-12312
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.