Skip to content
Fencer Intel
medium 5.0

CVE-2015-3204 json

libreswan 3.9 through 3.12 allows remote attackers to cause a denial of service (daemon restart) via an IKEv1 packet with (1) unassigned bi…

published 11y ago modified 4mo ago also EUVD-2015-3270

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

Summary

libreswan 3.9 through 3.12 allows remote attackers to cause a denial of service (daemon restart) via an IKEv1 packet with (1) unassigned bits set in the IPSEC DOI value or (2) the next payload value set to ISAKMP_NEXT_SAK.

Patch / fix

  • libreswan RHEL 7 3.12-10.1.el7_1
  • libreswan RHEL 7 3.12-10.1.ael7b_1

red hat advisories RHSA-2015:1154

Is CVE-2015-3204 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 Fencer

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-2015-3204 updated cvss 4.3

libreswan: crafted IKE packet causes daemon restart

  • Red Hat Enterprise Linux Client (v. 7) libreswan 3.12-10.1.el7_1 Red Hat Enterprise Linux Server (v. 7) libreswan 3.12-10.1.el7_1, libreswan 3.12-10.1.ael7b_1 Red Hat Enterprise Linux Workstation (v. 7) libreswan 3.12-10.1.el7_1
    fixed: vendor fix RHSA-2015:1154
  • Red Hat Enterprise Linux 5 openswan Red Hat Enterprise Linux 6 openswan
    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

2.60% chance of exploitation in the next 30 days, higher than 85% 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-20 Improper Input Validation

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.