CVE-2010-4237

Mercurial before 1.6.4 fails to verify the Common Name field of SSL certificates which allows remote attackers who acquire a certificate signed by a Certificate Authority to perform a man-in-the-middle attack.

Published: 2019-10-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2010-4237 is rated Moderate Risk (42.3/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.81%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2010-4237

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.31% 0.81% +0.51%
2 2025-03-30 1.05% 0.31% -0.74%
3 2025-03-29 — 1.05% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2010-4237

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2010-4237

GitHub Security Advisory for CVE-2010-4237

GHSA-7gf7-7wx4-mxmw · Severity: medium · Ecosystem: pip — Mercurial Improper Certificate Validation vulnerability

OS Trackers for CVE-2010-4237

vendor priority summary link
debian low CVE-2010-4237 low priority: Debian including 1 source packages (mercurial), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2010-4237
redhat medium — https://access.redhat.com/security/cve/CVE-2010-4237
ubuntu low CVE-2010-4237 low priority: Ubuntu including 1 source packages (mercurial), 9 status rows across 9 suites (hardy, lucid, natty, oneiric, precise, quantal, raring, saucy, upstream): not-affected 6, ignored 2, released 1. https://ubuntu.com/security/CVE-2010-4237

Affected software / configurations for CVE-2010-4237

Vendor Product Version Raw CPE
mercurial mercurial < 1.6.4 cpe:2.3:a:mercurial:mercurial:*:*:*:*:*:*:*:*

References for CVE-2010-4237

cvelogic Threat Intelligence