# CVE-2012-6709: Security feature bypass in n/a

> Attackers can bypass SSL certificate validation in ELinks and Twibright Links, enabling man-in-the-middle attacks against secure connections.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 23 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2012-6709, GHSA-8758-mxx4-h8h8, UBUNTU-CVE-2012-6709

## What is CVE-2012-6709?

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

### Official description

ELinks 0.12 and Twibright Links 2.3 have Missing SSL Certificate Validation.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2012-6709?

It affects 2 products.


Products: Elinks Elinks, Twibright Links.

## How do I fix CVE-2012-6709?

Upgrade to a fixed version.

## Is CVE-2012-6709 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7224](https://insights.sbomify.com/CVE-2008-7224/): Memory corruption in n/a (high 7.8)
- [CVE-2006-5925](https://insights.sbomify.com/CVE-2006-5925/): Command injection in n/a (high 7.5)
- [CVE-2012-4545](https://insights.sbomify.com/CVE-2012-4545/): Auth bypass in n/a (medium 5.1)
- [CVE-2002-1405](https://insights.sbomify.com/CVE-2002-1405/): Other in n/a (medium 5.0)
- [CVE-2007-2027](https://insights.sbomify.com/CVE-2007-2027/): Other in n/a (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-6709 and fix it if it is affected.

What it is: CVE-2012-6709 is a medium-severity vulnerability in n/a, published on 23 Feb 2018. 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-2012-6709 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-2012-6709/ (Markdown: https://insights.sbomify.com/CVE-2012-6709/index.md)
```

## Sources

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

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