# CVE-2014-3230: Security feature bypass in LWP::Protocol::https

> Attackers can disable SSL certificate validation in libwww-perl by setting specific environment variables, allowing man-in-the-middle attacks.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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:** 28 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2014-3230, DEBIAN-CVE-2014-3230, GHSA-7x2q-v99p-jm92, MGASA-2014-0257, UBUNTU-CVE-2014-3230, USN-2292-1, openSUSE-SU-2024:10239-1

## What is CVE-2014-3230?

CVE-2014-3230 is a medium-severity vulnerability in libwww-perl LWP::Protocol::https, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The libwww-perl LWP::Protocol::https module 6.04 through 6.06 for Perl, when using IO::Socket::SSL as the SSL socket class, allows attackers to disable server certificate validation via the (1) HTTPS_CA_DIR or (2) HTTPS_CA_FILE environment variable.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2014-3230?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-LWP-Protocol-https` | openSUSE:Tumbleweed | All versions | 6.06-1.4 |

Products: Lwp\ \.

## How do I fix CVE-2014-3230?

Upgrade to a fixed version.

## Is CVE-2014-3230 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3230 and fix it if it is affected.

What it is: CVE-2014-3230 is a medium-severity vulnerability in libwww-perl LWP::Protocol::https, published on 28 Jan 2020. 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-2014-3230 in the wild and no public exploit code.

Affected product: libwww-perl LWP::Protocol::https. 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-2014-3230/ (Markdown: https://insights.sbomify.com/CVE-2014-3230/index.md)
```

## Sources

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

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