libreswan 3.28

CPE Details

libreswan 3.28
3.28
2019-05-24
16h43 +00:00
2019-05-24
16h43 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:libreswan:libreswan:3.28:*:*:*:*:*:*:*

Informations

Vendor

libreswan

Product

libreswan

Version

3.28

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2023-38710 2023-08-24 22h00 +00:00 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.
6.5
Moyen
CVE-2023-38712 2023-08-24 22h00 +00:00 An issue was discovered in Libreswan 3.x and 4.x before 4.12. When an IKEv1 ISAKMP SA Informational Exchange packet contains a Delete/Notify payload followed by further Notifies that act on the ISAKMP SA, such as a duplicated Delete/Notify message, a NULL pointer dereference on the deleted state causes the pluto daemon to crash and restart.
6.5
Moyen
CVE-2023-30570 2023-05-27 22h00 +00:00 pluto in Libreswan before 4.11 allows a denial of service (responder SPI mishandling and daemon crash) via unauthenticated IKEv1 Aggressive Mode packets. The earliest affected version is 3.28.
7.5
Haute
CVE-2020-1763 2020-05-12 11h41 +00:00 An 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 could use this flaw to crash libreswan by sending specially-crafted IKEv1 Informational Exchange packets. The daemon respawns after the crash.
7.5
Haute
CVE-2019-10155 2019-06-12 11h51 +00:00 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.
3.1
Bas