# CVE-2008-2420: Security feature bypass in n/a

> Remote attackers can bypass access restrictions by using revoked certificates due to improper CRL checking in stunnel's OCSP functionality.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-2420, GHSA-7266-wh6x-6jjw

## What is CVE-2008-2420?

CVE-2008-2420 is a medium-severity vulnerability in n/a, published on 23 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OCSP functionality in stunnel before 4.24 does not properly search certificate revocation lists (CRL), which allows remote attackers to bypass intended access restrictions by using revoked certificates.

Weakness: CWE-264

## Which versions are affected by CVE-2008-2420?

It affects 1 product.


Products: Stunnel Stunnel.

## How do I fix CVE-2008-2420?

Upgrade to a fixed version.

## Is CVE-2008-2420 being exploited?

There is no known exploitation of CVE-2008-2420 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2001-0060](https://insights.sbomify.com/CVE-2001-0060/): Other in n/a (critical 10.0)
- [CVE-2011-2940](https://insights.sbomify.com/CVE-2011-2940/): Memory corruption in n/a (critical 9.3)
- [CVE-2021-20230](https://insights.sbomify.com/CVE-2021-20230/): Auth bypass in stunnel (high 7.5)
- [CVE-2008-2400](https://insights.sbomify.com/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)
- [CVE-2013-1762](https://insights.sbomify.com/CVE-2013-1762/): Integer overflow in n/a (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2420 and fix it if it is affected.

What it is: CVE-2008-2420 is a medium-severity vulnerability in n/a, published on 23 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-2420 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-2420/ (Markdown: https://insights.sbomify.com/CVE-2008-2420/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-2420
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-2420
- OSV: https://osv.dev/vulnerability/CVE-2008-2420

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-2420/
Summaries are generated and may contain mistakes; the official description above is the record.