Skip to content
Fencer Intel
medium 5.0

CVE-2014-9221 json

strongSwan 4.5.x through 5.2.x before 5.2.1 allows remote attackers to cause a denial of service (invalid pointer dereference) via a crafte…

published 2015-01-07 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9046

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.8%
EPSS 3.8% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

strongSwan 4.5.x through 5.2.x before 5.2.1 allows remote attackers to cause a denial of service (invalid pointer dereference) via a crafted IKEv2 Key Exchange (KE) message with Diffie-Hellman (DH) group 1025.

Patch / fix

  • strongswan Debian 14, Debian 13, Debian 12 5.2.1-5

debian advisories DEBIAN-CVE-2014-9221

  • strongswan Ubuntu 14.04 LTS 5.1.2-0ubuntu2.2

ubuntu advisories UBUNTU-CVE-2014-9221

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • strongswan SLED 12 5.1.3-9.1
  • strongswan SLES for SAP 12, SLES 12 5.1.3-9.2

suse advisories SUSE-SU-2015:0281-1

  • strongswan openSUSE Tumbleweed 5.3.5-1.1

opensuse advisories openSUSE-SU-2024:10579-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-9221 updated cvss 4.3

strongswan: denial-of-service vulnerability in libtls when processing crafted Key Exchange payload

  • Red Hat Enterprise Linux 7 strongimcv
    not 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

3.82% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-19 Data Processing Errors

References

Sources

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.