Back to bug 2225368
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| TEJ RATHI | 2023-07-25 05:37:12 UTC | CC | security-response-team | |
| TEJ RATHI | 2023-07-25 05:40:15 UTC | Blocks | 2225370 | |
| TEJ RATHI | 2023-07-25 05:47:06 UTC | CC | dueno | |
| TEJ RATHI | 2023-07-25 05:55:27 UTC | Depends On | 2215956 | |
| TEJ RATHI | 2023-07-25 05:55:37 UTC | Depends On | 2215955 | |
| TEJ RATHI | 2023-08-09 03:56:50 UTC | Alias | CVE-2023-38710 | |
| Summary | EMBARGOED libreswan: Invalid IKEv2 REKEY proposal causes restart | EMBARGOED CVE-2023-38710 libreswan: Invalid IKEv2 REKEY proposal causes restart | ||
| TEJ RATHI | 2023-08-09 05:20:09 UTC | Doc Text | An assertion failure flaw was found in Libreswan package which occurs when processing IKEv2 REKEY requests. 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). A malicious client or attacker could send a malformed IKEv2 REKEY packet would cause a crash and restart of the libreswan pluto daemon. When sent continuously, this could lead to a denial of service attack. | |
| TEJ RATHI | 2023-08-09 05:23:53 UTC | Comment | 0 | updated |
| TEJ RATHI | 2023-08-09 05:29:23 UTC | Summary | EMBARGOED CVE-2023-38710 libreswan: Invalid IKEv2 REKEY proposal causes restart | CVE-2023-38710 libreswan: Invalid IKEv2 REKEY proposal causes restart |
| Deadline | 2023-08-07 | |||
| Group | qe_staff, security | |||
| TEJ RATHI | 2023-08-09 05:39:34 UTC | Depends On | 2230238 | |
| RaTasha Tillery-Smith | 2023-08-09 14:16:29 UTC | Doc Text | An assertion failure flaw was found in Libreswan package which occurs when processing IKEv2 REKEY requests. 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). A malicious client or attacker could send a malformed IKEv2 REKEY packet would cause a crash and restart of the libreswan pluto daemon. When sent continuously, this could lead to a denial of service attack. | An assertion failure flaw was found in the Libreswan package that occurs when processing IKEv2 REKEY requests. When an IKEv2 Child SA REKEY packet contains an invalid IPsec protocol ID number of 0 or 1, an error notification 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). This flaw allows a malicious client or attacker to send a malformed IKEv2 REKEY packet, causing a crash and restarting the libreswan pluto daemon. When sent continuously, this could lead to a denial of service attack. |
Back to bug 2225368