Reachable Assertion Affecting libreswan package, versions <0:4.12-1.el9


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.07% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-LIBRESWAN-7875244
  • published3 Sept 2024
  • disclosed8 Aug 2023

Introduced: 8 Aug 2023

CVE-2023-38710  (opens in a new tab)
CWE-617  (opens in a new tab)

How to fix?

Upgrade RHEL:9 libreswan to version 0:4.12-1.el9 or higher.
This issue was patched in RHSA-2023:6549.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libreswan package and not the libreswan package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

An issue was discovered in Libreswan before 4.12. When an IKEv2 Child SA REKEY packet contains an invalid IPsec protocol ID number of 0 or 1, an error notify INVALID_SPI is sent back. The notify payload's protocol ID is copied from the incoming packet, but the code that verifies outgoing packets fails an assertion that the protocol ID must be ESP (2) or AH(3) and causes the pluto daemon to crash and restart. NOTE: the earliest affected version is 3.20.

CVSS Scores

version 3.1