CVE-2008-3652 json
src/racoon/handler.c in racoon in ipsec-tools does not remove an "orphaned ph1" (phase 1) handle when it has been initiated remotely, which…
published 2008-08-13 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3638
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
src/racoon/handler.c in racoon in ipsec-tools does not remove an "orphaned ph1" (phase 1) handle when it has been initiated remotely, which allows remote attackers to cause a denial of service (resource consumption).
Patch / fix
- ipsec-tools RHEL 3 0.2.5-0.7.rhel3.5
- ipsec-tools RHEL 4 0.3.3-7.el4_7
- ipsec-tools RHEL 5 0.6.5-9.el5_2.3
red hat advisories RHSA-2008:0849
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2008-3652 updated
ipsec-tools: racoon orphaned ph1s memory leak
-
Red Hat Desktop version 3 ipsec-tools 0.2.5-0.7.rhel3.5 Red Hat Enterprise Linux (v. 5 server) ipsec-tools 0.6.5-9.el5_2.3 Red Hat Enterprise Linux AS version 3 ipsec-tools 0.2.5-0.7.rhel3.5 Red Hat Enterprise Linux AS version 4 ipsec-tools 0.3.3-7.el4_7 Red Hat Enterprise Linux Desktop (v. 5 client) ipsec-tools 0.6.5-9.el5_2.3 Red Hat Enterprise Linux Desktop version 4 ipsec-tools 0.3.3-7.el4_7fixed: vendor fix RHSA-2008:0849
+4 more productsfewer
Red Hat Enterprise Linux ES version 3 ipsec-tools 0.2.5-0.7.rhel3.5 Red Hat Enterprise Linux ES version 4 ipsec-tools 0.3.3-7.el4_7 Red Hat Enterprise Linux WS version 3 ipsec-tools 0.2.5-0.7.rhel3.5 Red Hat Enterprise Linux WS version 4 ipsec-tools 0.3.3-7.el4_7
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.44% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
mandriva.com
/security/advisories?name=MDVSA-2008:181
vendor-advisory
-
lists.apple.com
/archives/security-announce/2009/Jun/msg00005.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2009/May/msg00002.html
vendor-advisory
-
security.gentoo.org
/glsa/glsa-200812-03.xml
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2009-02/msg00002.html
vendor-advisory
-
ubuntu.com
/usn/usn-641-1
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2008-11/msg00001.html
vendor-advisory
-
redhat.com
/support/errata/RHSA-2008-0849.html
vendor-advisory
- support.apple.com /kb/HT3639
-
vupen.com
/english/advisories/2009/1621
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44424
vdb-entry
- support.apple.com /kb/HT3549
-
securitytracker.com
/id?1020692
vdb-entry
-
secunia.com
/advisories/35074
third-party-advisory
-
vupen.com
/english/advisories/2008/2378
vdb-entry
-
securityfocus.com
/bid/30657
vdb-entry
-
secunia.com
/advisories/32971
third-party-advisory
-
vupen.com
/english/advisories/2008/2844
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10448
vdb-entry, signature
-
secunia.com
/advisories/31478
third-party-advisory
-
secunia.com
/advisories/32759
third-party-advisory
-
secunia.com
/advisories/31624
third-party-advisory
-
us-cert.gov
/cas/techalerts/TA09-133A.html
third-party-advisory, us-government-resource
-
vupen.com
/english/advisories/2009/1297
vdb-entry
-
sourceforge.net
/mailarchive/forum.php?thread_name=48a0c7a0.qPeWZAE0PY8bDDq%2B%25olel%40ans.pl&forum_name=ipsec-tools-devel
mailing-list
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=501026
Sources
- CVE List CVE-2008-3652
- NVD CVE-2008-3652
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.