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

> Man-in-the-middle attackers can spoof SSL servers by exploiting improper domain-name comparison in X.509 certificates within macOS libsecurity.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Aug 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-927q-r643-v6jf

## What is CVE-2010-1802?

CVE-2010-1802 is a medium-severity vulnerability in Apple Mac Os X, published on 25 Aug 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

libsecurity in Apple Mac OS X 10.5.8 and 10.6.4 does not properly perform comparisons to domain-name strings in X.509 certificates, which allows man-in-the-middle attackers to spoof SSL servers via a certificate associated with a similar domain name, as demonstrated by use of a www.example.con certificate to spoof www.example.com.

Weakness: CWE-287 (Improper Authentication)

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

It affects 3 products.


Products: Apple Libsecurity, Apple Mac Os X, Apple Mac Os X Server.

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

No fix has been published for CVE-2010-1802 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-1802 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2010-1802 is a medium-severity vulnerability in Apple Mac Os X, published on 25 Aug 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-1802 in the wild and no public exploit code.

Affected product: Apple Mac Os X. 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-1802/ (Markdown: https://insights.sbomify.com/CVE-2010-1802/index.md)
```

## Sources

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

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