CVE-2009-2661 json
The asn1_length function in strongSwan 2.8 before 2.8.11, 4.2 before 4.2.17, and 4.3 before 4.3.3 does not properly handle X.509 certificat…
published 2009-08-04 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2654
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
The asn1_length function in strongSwan 2.8 before 2.8.11, 4.2 before 4.2.17, and 4.3 before 4.3.3 does not properly handle X.509 certificates with crafted Relative Distinguished Names (RDNs), which allows remote attackers to cause a denial of service (pluto IKE daemon crash) via malformed ASN.1 data. NOTE: this is due to an incomplete fix for CVE-2009-2185.
Patch / fix
- strongswan Debian 14, Debian 13, Debian 12 4.3.2-1.1
debian advisories DEBIAN-CVE-2009-2661
Exploit prediction
1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
download.strongswan.org
/patches/07_asn1_length_patch/strongswan-4.x.x_asn1_length.patch
patch
-
lists.strongswan.org
/pipermail/announce/2009-July/000056.html
mailing-list, patch
-
lists.opensuse.org
/opensuse-security-announce/2009-11/msg00004.html
vendor-advisory
-
debian.org
/security/2009/dsa-1899
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2009-10/msg00001.html
vendor-advisory
-
openwall.com
/lists/oss-security/2009/07/27/1
mailing-list
-
secunia.com
/advisories/36922
third-party-advisory
-
vupen.com
/english/advisories/2009/2247
vdb-entry
- up2date.astaro.com /2009/08/up2date_7505_released.html
- download.strongswan.org /patches/07_asn1_length_patch/strongswan-4.3.x_asn1_length.patch
Sources
- CVE List CVE-2009-2661
- NVD CVE-2009-2661
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.