CVE-2008-2400 stunnel stunnel
stunnel stunnel: no CVSS score yet. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
Unspecified vulnerability in stunnel before 4.23, when running as a service on Windows, allows local users to gain privileges via unknown attack vectors.
- EPSS
- 0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-264 Permissions, Privileges, and Access Controls
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://secunia.com/advisories/30297
Ask an AI about this CVE
Show the prompt
Explain CVE-2008-2400 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2008-2400?via=ask-ai-copy and https://cve.bz/cve/CVE-2008-2400?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2008-2400 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| stunnel:stunnel | 0.1 |
| stunnel:stunnel | 1.0 |
| stunnel:stunnel | 1.1 |
| stunnel:stunnel | 1.2 |
| stunnel:stunnel | 1.3 |
| stunnel:stunnel | 1.4 |
| stunnel:stunnel | 1.5 |
| stunnel:stunnel | 1.6 |
| stunnel:stunnel | 2.0 |
| stunnel:stunnel | 2.1 |
| stunnel:stunnel | 3.0 |
| stunnel:stunnel | 3.0:b1 |
| stunnel:stunnel | 3.0:b2 |
| stunnel:stunnel | 3.0:b3 |
| stunnel:stunnel | 3.0:b4 |
| stunnel:stunnel | 3.0:b5 |
| stunnel:stunnel | 3.0:b6 |
| stunnel:stunnel | 3.0:b7 |
| stunnel:stunnel | 3.1 |
| stunnel:stunnel | 3.2 |
| stunnel:stunnel | 3.3 |
| stunnel:stunnel | 3.4a |
| stunnel:stunnel | 3.5 |
| stunnel:stunnel | 3.6 |
| stunnel:stunnel | 3.7 |
| stunnel:stunnel | 3.8 |
| stunnel:stunnel | 3.8:p1 |
| stunnel:stunnel | 3.8:p2 |
| stunnel:stunnel | 3.8:p3 |
| stunnel:stunnel | 3.8:p4 |
| stunnel:stunnel | 3.9 |
| stunnel:stunnel | 3.10 |
| stunnel:stunnel | 3.11 |
| stunnel:stunnel | 3.12 |
| stunnel:stunnel | 3.13 |
| stunnel:stunnel | 3.14 |
| stunnel:stunnel | 3.15 |
| stunnel:stunnel | 3.16 |
| stunnel:stunnel | 3.17 |
| stunnel:stunnel | 3.18 |
| stunnel:stunnel | 3.19 |
| stunnel:stunnel | 3.20 |
| stunnel:stunnel | 3.21 |
| stunnel:stunnel | 3.21a |
| stunnel:stunnel | 3.21b |
| stunnel:stunnel | 3.21c |
| stunnel:stunnel | 3.22 |
| stunnel:stunnel | 3.24 |
| stunnel:stunnel | 4.0 |
| stunnel:stunnel | 4.01 |
| stunnel:stunnel | 4.02 |
| stunnel:stunnel | 4.03 |
| stunnel:stunnel | 4.04 |
| stunnel:stunnel | 4.05 |
| stunnel:stunnel | 4.06 |
| stunnel:stunnel | 4.07 |
| stunnel:stunnel | 4.08 |
| stunnel:stunnel | 4.09 |
| stunnel:stunnel | 4.10 |
| stunnel:stunnel | 4.11 |
| stunnel:stunnel | 4.12 |
| stunnel:stunnel | 4.13 |
| stunnel:stunnel | 4.14 |
| stunnel:stunnel | 4.15 |
| stunnel:stunnel | 4.16 |
| stunnel:stunnel | 4.17 |
| stunnel:stunnel | 4.18 |
| stunnel:stunnel | 4.19 |
| stunnel:stunnel | 4.20 |
| stunnel:stunnel | 4.21 |
| stunnel:stunnel | 4.22 |
References
- http://secunia.com/advisories/30297
- http://stunnel.mirt.net/pipermail/stunnel-announce/2008-May/000034.html
- http://www.securityfocus.com/bid/29285
- http://www.securitytracker.com/id?1020049
- http://www.vupen.com/english/advisories/2008/1568/references
- https://exchange.xforce.ibmcloud.com/vulnerabilities/42526