First published: Tue Jul 25 2023(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Libreswan Libreswan | >=3.20<4.12 | |
redhat/libreswan | <4.12 | 4.12 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2023-38710 is high with a CVSS score of 7.5.
The affected software for CVE-2023-38710 is Libreswan versions 3.20 to 4.12.
To fix CVE-2023-38710, update Libreswan to version 4.12 or higher.
If an IKEv2 Child SA REKEY packet contains an invalid IPsec protocol ID number (0 or 1), an error notify INVALID_SPI is sent back.
You can find more information about CVE-2023-38710 at the following references: [here](https://github.com/libreswan/libreswan/tags) and [here](https://libreswan.org/security/CVE-2023-38710/).