gsd-2024-3652
Vulnerability from gsd
Modified
2024-04-11 05:03
Details
The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan's default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.
Aliases
{
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2024-3652"
],
"details": "The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan\u0027s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected.",
"id": "GSD-2024-3652",
"modified": "2024-04-11T05:03:27.386137Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "security@libreswan.org",
"ID": "CVE-2024-3652",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "libreswan",
"version": {
"version_data": [
{
"version_value": "not down converted",
"x_cve_json_5_version_data": {
"defaultStatus": "unaffected",
"versions": [
{
"lessThanOrEqual": "4.14",
"status": "affected",
"version": "3.22",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.0"
}
]
}
}
]
}
}
]
},
"vendor_name": "The Libreswan Project (www.libreswan.org)"
}
]
}
},
"configuration": [
{
"lang": "en",
"value": "The vulnerability can only be triggered for connections with ikev2=no that do not specify an esp= option."
}
],
"credits": [
{
"lang": "en",
"value": "github user X1AOxiang"
}
],
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan\u0027s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "IKEv1 with default AH/ESP configuration can cause libreswan to abort and restart"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://libreswan.org/security/CVE-2024-3652",
"refsource": "MISC",
"url": "https://libreswan.org/security/CVE-2024-3652"
}
]
},
"solution": [
{
"lang": "en",
"value": "This issue is fixed in 4.15 and all later versions."
}
],
"work_around": [
{
"lang": "en",
"value": "As a workaround, adding an esp= line to all IKEv1 connections works around the issue. An example covering most common default configurations would be: esp=aes-sha2_512,aes-sha1,aes-sha2_256,aes-md5,3des-sha1,3des-md5. "
}
]
},
"nvd.nist.gov": {
"cve": {
"descriptions": [
{
"lang": "en",
"value": "The Libreswan Project was notified of an issue causing libreswan to restart when using IKEv1 without specifying an esp= line. When the peer requests AES-GMAC, libreswan\u0027s default proposal handler causes an assertion failure and crashes and restarts. IKEv2 connections are not affected."
},
{
"lang": "es",
"value": "Se notific\u00f3 a Libreswan Project sobre un problema que provocaba que libreswan se reiniciara al usar IKEv1 sin especificar una l\u00ednea esp=. Cuando el par solicita AES-GMAC, el controlador de propuestas predeterminado de libreswan provoca un error de aserci\u00f3n, falla y se reinicia. Las conexiones IKEv2 no se ven afectadas."
}
],
"id": "CVE-2024-3652",
"lastModified": "2024-04-11T12:47:44.137",
"metrics": {},
"published": "2024-04-11T02:15:47.790",
"references": [
{
"source": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"url": "https://libreswan.org/security/CVE-2024-3652"
}
],
"sourceIdentifier": "d42dc95b-23f1-4e06-9076-20753a0fb0df",
"vulnStatus": "Awaiting Analysis"
}
}
}
}
Loading...
Loading...
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.