Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2009-0790: The pluto IKE daemon in Openswan and Strongswan IPsec 2.6 before 2.6.21 and 2.4 before 2.4.14, and Strongswan 4.2 before 4.2.14 and 2.8…

MediumCVSS 5.0 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 88.3% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: strongswan (Debian:12) 4.2.14-1; openswan (Debian:4.0) 1:2.4.6+dfsg.2-1.1+etch1; strongswan (Debian:4.0) 2.8.0+dfsg-1+etch1.

Low priority for now. Upgrade to strongswan (Debian:12) 4.2.14-1; openswan (Debian:4.0) 1:2.4.6+dfsg.2-1.1+etch1; strongswan (Debian:4.0) 2.8.0+dfsg-1+etch1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The pluto IKE daemon in Openswan and Strongswan IPsec 2.6 before 2.6.21 and 2.4 before 2.4.14, and Strongswan 4.2 before 4.2.14 and 2.8 before 2.8.9, allows remote attackers to cause a denial of service (daemon crash and restart) via a crafted (1) R_U_THERE or (2) R_U_THERE_ACK Dead Peer Detection (DPD) IPsec IKE Notification message that triggers a NULL pointer dereference related to inconsistent ISAKMP state and the lack of a phase2 state association in DPD.

Published
Apr 1, 2009
Updated
Jun 16, 2026
EPSS
3.2% · 88th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2009-0790

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
strongswanstrongswan
xeleranceopenswan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • strongswan strongswan2.4.0
  • strongswan strongswan2.4.0a
  • strongswan strongswan2.4.1
  • strongswan strongswan2.4.2
  • strongswan strongswan2.4.3
  • strongswan strongswan2.4.4
  • strongswan strongswan2.6.0
  • strongswan strongswan2.6.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12strongswanbefore 4.2.14-14.2.14-1
Debian:4.0openswanbefore 1:2.4.6+dfsg.2-1.1+etch11:2.4.6+dfsg.2-1.1+etch1
Debian:4.0strongswanbefore 2.8.0+dfsg-1+etch12.8.0+dfsg-1+etch1
Debian:5.0openswanbefore 1:2.4.12+dfsg-1.3+lenny11:2.4.12+dfsg-1.3+lenny1
Debian:5.0strongswanbefore 4.2.4-5+lenny14.2.4-5+lenny1
openSUSE:Tumbleweedstrongswanbefore 5.3.5-1.15.3.5-1.1
Red Hat:enterprise_linux:5::clientopenswanbefore 0:2.6.14-1.el5_3.20:2.6.14-1.el5_3.2
Red Hat:enterprise_linux:5::clientopenswan-debuginfobefore 0:2.6.14-1.el5_3.20:2.6.14-1.el5_3.2
Red Hat:enterprise_linux:5::clientopenswan-docbefore 0:2.6.14-1.el5_3.20:2.6.14-1.el5_3.2

Other highest-scoring records for the same primary product.

  • CVE-2023-41913strongSwan before 5.9.12 has a buffer overflow and possible unauthenticated remote code execution via a DH public value that exceeds the…
    40Plan
  • CVE-2023-26463strongSwan 5.9.8 and 5.9.9 potentially allows remote code execution because it uses a variable named "public" for two different purposes…
    40Plan
  • CVE-2015-3991strongSwan 5.2.2 and 5.3.0 allows remote attackers to cause a denial of service (daemon crash) or execute arbitrary code.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2008-4551Oct 14, 2008 · strongSwan 4.2.6 and earlier allows remote attackers to cause a denial of service (daemon crash) via an IKE_SA_INIT message with a large…
    21Monitor
  • Later →CVE-2009-1957Jun 7, 2009 · charon/sa/ike_sa.c in the charon daemon in strongSWAN before 4.3.1 allows remote attackers to cause a denial of service (NULL pointer…
    21Monitor
  • Later →CVE-2009-1958Jun 7, 2009 · charon/sa/tasks/child_create.c in the charon daemon in strongSWAN before 4.3.1 switches the NULL checks for TSi and TSr payloads, which…
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:openswan1:2.4.6+dfsg.2-1.1+etch1 · Debian:4.0Package registry (OSV)
debian:strongswan4.2.14-1 · Debian:12Package registry (OSV)
opensuse:strongswan5.3.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:openswan0:2.6.14-1.el5_3.2 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:openswan-debuginfo0:2.6.14-1.el5_3.2 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:openswan-doc0:2.6.14-1.el5_3.2 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

References

All records