# CVE-2014-0350: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof SSL servers by exploiting a flaw in X.509 certificate verification logic within the POCO C++ Libraries NetSSL component.

- **Severity:** Medium 6.4 (`AV:N/AC:L/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:** 26 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-0350, GHSA-whgv-p774-rw69, UBUNTU-CVE-2014-0350

## What is CVE-2014-0350?

CVE-2014-0350 is a medium-severity vulnerability in n/a, published on 26 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Poco::Net::X509Certificate::verify method in the NetSSL library in POCO C++ Libraries before 1.4.6p4 allows man-in-the-middle attackers to spoof SSL servers via crafted DNS PTR records that are requested during comparison of a server name to a wildcard domain name in an X.509 certificate.

Weakness: CWE-310

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

It affects 1 product.


Products: Pocoproject Poco C\+\+ Libraries.

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

Upgrade to a fixed version.

## Is CVE-2014-0350 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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