# CVE-2009-3024: Security feature bypass in n/a

> Remote attackers can bypass SSL certificate hostname verification in IO::Socket::SSL by exploiting prefix matching flaws, enabling man-in-the-middle attacks.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-3024, GHSA-5v53-7q2j-vjr2

## What is CVE-2009-3024?

CVE-2009-3024 is a medium-severity vulnerability in n/a, published on 31 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The verify_hostname_of_cert function in the certificate checking feature in IO-Socket-SSL (IO::Socket::SSL) 1.14 through 1.25 only matches the prefix of a hostname when no wildcard is used, which allows remote attackers to bypass the hostname check for a certificate.

Weakness: CWE-310

## Which versions are affected by CVE-2009-3024?

It affects 1 product.


Products: Io-Socket-Ssl Io-Socket-Ssl.

## How do I fix CVE-2009-3024?

Upgrade to a fixed version.

## Is CVE-2009-3024 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4334](https://insights.sbomify.com/CVE-2010-4334/): Security feature bypass in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3024 and fix it if it is affected.

What it is: CVE-2009-3024 is a medium-severity vulnerability in n/a, published on 31 Aug 2009. 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-2009-3024 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-2009-3024/ (Markdown: https://insights.sbomify.com/CVE-2009-3024/index.md)
```

## Sources

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

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