# CVE-2010-4334: Security feature bypass in n/a

> Remote attackers can bypass SSL certificate verification restrictions in the Perl IO::Socket::SSL module due to a fail-open error handling flaw.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/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:** 14 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2010-4501, DEBIAN-CVE-2010-4334, GHSA-rgc7-283p-45vh

## What is CVE-2010-4334?

CVE-2010-4334 is a medium-severity vulnerability in n/a, published on 14 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IO::Socket::SSL module 1.35 for Perl, when verify_mode is not VERIFY_NONE, fails open to VERIFY_NONE instead of throwing an error when a ca_file/ca_path cannot be verified, which allows remote attackers to bypass intended certificate restrictions.

Weakness: CWE-310

## Which versions are affected by CVE-2010-4334?

It affects 1 product.


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

## How do I fix CVE-2010-4334?

Upgrade to a fixed version.

## Is CVE-2010-4334 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3024](https://insights.sbomify.com/CVE-2009-3024/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4334 and fix it if it is affected.

What it is: CVE-2010-4334 is a medium-severity vulnerability in n/a, published on 14 Jan 2011. 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-2010-4334 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-2010-4334/ (Markdown: https://insights.sbomify.com/CVE-2010-4334/index.md)
```

## Sources

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

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