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

> Midori browser fails to verify X.509 certificates, allowing man-in-the-middle attackers to spoof HTTPS sites via crafted server certificates.

- **Severity:** Medium 5.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Oct 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-3900, GHSA-x27m-58m8-qvm6

## What is CVE-2010-3900?

CVE-2010-3900 is a medium-severity vulnerability in n/a, published on 12 Oct 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Midori before 0.2.5, when WebKitGTK+ before 1.1.14 or LibSoup before 2.29.91 is used, does not verify X.509 certificates, which allows man-in-the-middle attackers to spoof arbitrary https web sites via a crafted server certificate, a related issue to CVE-2010-3312.

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

It affects 1 product.


Products: Christian Dywan Midori.

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

Upgrade to a fixed version.

## Is CVE-2010-3900 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2010-3900 is a medium-severity vulnerability in n/a, published on 12 Oct 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-3900 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-3900/ (Markdown: https://insights.sbomify.com/CVE-2010-3900/index.md)
```

## Sources

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

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