Skip to content
Fencer Vulns
medium 5.0

CVE-2009-1632 json

Multiple memory leaks in Ipsec-tools before 0.7.2 allow remote attackers to cause a denial of service (memory consumption) via vectors invo…

published 2009-05-14 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1627

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

Multiple memory leaks in Ipsec-tools before 0.7.2 allow remote attackers to cause a denial of service (memory consumption) via vectors involving (1) signature verification during user authentication with X.509 certificates, related to the eay_check_x509sign function in src/racoon/crypto_openssl.c; and (2) the NAT-Traversal (aka NAT-T) keepalive implementation, related to src/racoon/nattraversal.c.

Patch / fix

  • ipsec-tools RHEL 5 0.6.5-13.el5_3.1

red hat advisories RHSA-2009:1036

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-2009-1632 updated cvss 4.3

ipsec-tools: multiple memory leaks fixed in 0.7.2

  • Red Hat Enterprise Linux 4 ipsec-tools
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux (v. 5 server) ipsec-tools 0.6.5-13.el5_3.1 Red Hat Enterprise Linux Desktop (v. 5 client) ipsec-tools 0.6.5-13.el5_3.1
    fixed: vendor fix RHSA-2009:1036

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

2.02% chance of exploitation in the next 30 days, higher than 81% 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-399 Resource Management Errors

References

Sources

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.