# CVE-2013-10001: HTC One/Sense Mail Client certificate validation

> Attackers can bypass certificate validation in the HTC Sense Mail Client, potentially enabling man-in-the-middle attacks on email traffic.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-mx89-3q43-9x7h

## What is CVE-2013-10001?

CVE-2013-10001 is a medium-severity vulnerability in HTC One, published on 17 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in HTC One/Sense 4.x. It has been rated as problematic. Affected by this issue is the certification validation of the mail client. An exploit has been disclosed to the public and may be used.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2013-10001?

It affects 1 product.


Products: Htc Mail.

## How do I fix CVE-2013-10001?

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

## Is CVE-2013-10001 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-10001 and fix it if it is affected.

What it is: CVE-2013-10001 is a medium-severity vulnerability in HTC One, published on 17 May 2022. 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-2013-10001 in the wild and no public exploit code.

Affected product: HTC One. 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-2013-10001/ (Markdown: https://insights.sbomify.com/CVE-2013-10001/index.md)
```

## Sources

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

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