CVE-2008-2400 Unspecified vulnerability in stunnel before 4.23, when running as a service on Windows, allows local users to gain privileges via unknown attack vectors.
High 7.2
Published
Updated
Check this codebase for CVE-2008-2400 and fix it if it is affected.
What it is: CVE-2008-2400 is a high-severity vulnerability in n/a, published on 22 May 2008.
Exploitation: There is no known exploitation of CVE-2008-2400 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2008-2400/ (Markdown: https://insights.sbomify.com/CVE-2008-2400/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2008-2400?
CVE-2008-2400 is a high-severity vulnerability in n/a, published on 22 May 2008.
Official description
Unspecified vulnerability in stunnel before 4.23, when running as a service on Windows, allows local users to gain privileges via unknown attack vectors.
Weakness: CWE-264
Which versions are affected by CVE-2008-2400?
It affects 1 product.
Products include Stunnel Stunnel.
How do I fix CVE-2008-2400?
No fix has been published for CVE-2008-2400 yet. Limit exposure of the affected software until one is available.
Is CVE-2008-2400 being exploited?
There is no known exploitation of CVE-2008-2400 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-r8p5-h86h-72h9.