Skip to content
Noroxi
CVE-2019-10155· NVD / CVE Program· CNA redhat

The Libreswan Project has found a vulnerability in the processing of IKEv1 informational exchange packets which are encrypted and integrity

The Libreswan Project has found a vulnerability in the processing of IKEv1 informational exchange packets which are encrypted and integrity protected using the established IKE SA encryption and integrity keys, but as a receiver, the integrity check value was not verified. This issue affects versions before 3.29.

LowCVSS 3.1 · v3.1—No exploit Fix available
Published
Jun 12, 2019
Updated
Jun 16, 2026
EPSS
0.5% · 41th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
12 / 40 · 3.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CNA vs NVD score

NVD
3.1
CNA · redhat
3.1
agree

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
libreswanlibreswan
strongswanstrongswan
xeleranceopenswan
fedoraprojectfedora
redhatenterprise linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora29
  • fedoraproject fedora30
  • libreswan libreswanbefore 3.29
  • redhat enterprise linux8.0
  • strongswan strongswanbefore 5.0.0
  • xelerance openswanall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • the libreswan Project libreswan

    • 3.29affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libreswanbefore 3.27-63.27-6
Debian:12strongswanbefore 5.1.0-15.1.0-1
Red Hat:enterprise_linux:8::appstreamlibreswanbefore 0:3.29-6.el80:3.29-6.el8
Red Hat:enterprise_linux:8::appstreamlibreswan-debuginfobefore 0:3.29-6.el80:3.29-6.el8
Red Hat:enterprise_linux:8::appstreamlibreswan-debugsourcebefore 0:3.29-6.el80:3.29-6.el8

Other highest-scoring records for the same primary product.

  • CVE-2013-7283Race condition in the libreswan.spec files for Red Hat Enterprise Linux (RHEL) and Fedora packages in libreswan 3.6 has unspecified impact a
    37Monitor
  • CVE-2022-23094Libreswan 4.2 through 4.5 allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted IKE
    31Monitor
  • CVE-2020-1763An out-of-bounds buffer read flaw was found in the pluto daemon of libreswan from versions 3.27 till 3.31 where, an unauthenticated attacker
    31Monitor
  • CVE-2019-12312In Libreswan 3.27 an assertion failure can lead to a pluto IKE daemon restart.
    31Monitor
  • CVE-2016-5391libreswan before 3.18 allows remote attackers to cause a denial of service (NULL pointer dereference and pluto daemon restart).
    31Monitor
  • CVE-2016-5361programs/pluto/ikev1.c in libreswan before 3.17 retransmits in initial-responder states, which allows remote attackers to cause a denial of
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libreswan3.27-6 · Debian:12Package registry (OSV)
debian:strongswan5.1.0-1 · Debian:12Package registry (OSV)
red hat:libreswan0:3.29-6.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libreswan-debuginfo0:3.29-6.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:libreswan-debugsource0:3.29-6.el8 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records