CVE-2008-4190: The IPSEC livetest tool in Openswan 2.4.12 and earlier, and 2.6.x through 2.6.16, allows local users to overwrite arbitrary files and…
Noroxi assessment
Priority: Monitor (action score 17/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.5% of all records.
- Fixed version: openswan (Debian:4.0) 1:2.4.6+dfsg.2-1.1+etch1; openswan (Debian:5.0) 1:2.4.12+dfsg-1.3+lenny1; openswan (Red Hat:enterprise_linux:5::client) 0:2.6.14-1.el5_3.2.
Low priority for now. Upgrade to openswan (Debian:4.0) 1:2.4.6+dfsg.2-1.1+etch1; openswan (Debian:5.0) 1:2.4.12+dfsg-1.3+lenny1; openswan (Red Hat:enterprise_linux:5::client) 0:2.6.14-1.el5_3.2 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 IPSEC livetest tool in Openswan 2.4.12 and earlier, and 2.6.x through 2.6.16, allows local users to overwrite arbitrary files and execute arbitrary code via a symlink attack on the (1) ipseclive.conn and (2) ipsec.olts.remote.log temporary files. NOTE: in many distributions and the upstream version, this tool has been disabled.
- Published
- Sep 24, 2008
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-59
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| openswan | openswan | cpe:2.3:a:openswan:openswan |
| xelerance | openswan | cpe:2.3:a:xelerance:openswan |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openswan openswan1.0.4
- openswan openswan1.0.5
- openswan openswan1.0.6
- openswan openswan1.0.7
- openswan openswan1.0.8
- openswan openswan1.0.9
- openswan openswan2.1.1
- openswan openswan2.1.2
+12 more rows
- openswan openswan2.1.4
- openswan openswan2.1.5
- openswan openswan2.1.6
- openswan openswan2.2
- openswan openswan2.3
- xelerance openswan2.3.1
- xelerance openswan2.4.0
- xelerance openswan2.4.2
- xelerance openswan2.4.4
- xelerance openswan2.6.03
- xelerance openswan2.6.04
- xelerance openswan2.6.05
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:4.0 | openswan | before 1:2.4.6+dfsg.2-1.1+etch1 | 1:2.4.6+dfsg.2-1.1+etch1 |
| Debian:5.0 | openswan | before 1:2.4.12+dfsg-1.3+lenny1 | 1:2.4.12+dfsg-1.3+lenny1 |
| Red Hat:enterprise_linux:5::client | openswan | before 0:2.6.14-1.el5_3.2 | 0:2.6.14-1.el5_3.2 |
| Red Hat:enterprise_linux:5::client | openswan-debuginfo | before 0:2.6.14-1.el5_3.2 | 0:2.6.14-1.el5_3.2 |
| Red Hat:enterprise_linux:5::client | openswan-doc | before 0:2.6.14-1.el5_3.2 | 0:2.6.14-1.el5_3.2 |
Same product
openswan: all recordsOther highest-scoring records for the same primary product.
- CVE-2004-0590FreeS/WAN 1.x and 2.x, and other related products including superfreeswan 1.x, openswan 1.x before 1.0.6, openswan 2.x before 2.1.4, and…41Plan
- CVE-2005-3671The Internet Key Exchange version 1 (IKEv1) implementation in Openswan 2 (openswan-2) before 2.4.4, and freeswan in SUSE LINUX 9.1 before 2.33Monitor
- CVE-2005-0162Stack-based buffer overflow in the get_internal_addresses function in the pluto application for Openswan 1.x before 1.0.9, and Openswan 2.x…29Monitor
Published before and after this one in the same product
- Later →CVE-2011-2147May 20, 2011 · Openswan 2.2.x does not properly restrict permissions for (1) /var/run/starter.pid, related to starter.c in the IPsec starter, and (2)…14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:openswan | 1:2.4.6+dfsg.2-1.1+etch1 · Debian:4.0 | Package registry (OSV) |
| red hat:openswan | 0:2.6.14-1.el5_3.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:openswan-debuginfo | 0:2.6.14-1.el5_3.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
| red hat:openswan-doc | 0:2.6.14-1.el5_3.2 · Red Hat:enterprise_linux:5::client | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | local | 2009-07-13 |
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.
- Published
- First PoC+292 d
- TodayNov 16, 2026+6627 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
AV:L/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (13 more)Show less
- dev.gentoo.org/~rbu/security/debiantemp/openswan
- secunia.com/advisories/34182
- secunia.com/advisories/34472
- www.debian.org/security/2009/dsa-1760
- www.openwall.com/lists/oss-security/2008/10/30/2
- www.redhat.com/support/errata/RHSA-2009-0402.html
- www.securityfocus.com/archive/1/501624/100/0/threaded
- www.securityfocus.com/archive/1/501640/100/0/threaded
- www.securityfocus.com/bid/31243
- bugs.gentoo.org/show_bug.cgi?id=235770
- bugzilla.redhat.com/show_bug.cgi?id=460425
- exchange.xforce.ibmcloud.com/vulnerabilities/45250
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10078
Vendor advisories and official records. Exploit/PoC links are deliberately left out.