Debian LinuxOperating system · Debian
CVE-2018-1000132
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMercurial version 4.5 and earlier contains a Incorrect Access Control (CWE-285) vulnerability in Protocol server that can result in Unauthorized data access. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 4.5.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMercurial versions 4.5 and earlier contain an incorrect access control vulnerability (CWE-285) in the protocol server component. The vulnerability allows unauthorized data access through network connectivity to the protocol server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 7.0= 8.0< 4.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Mercurial versionRun `hg --version` and examine the version number in the outputAffected if The version displayed is earlier than 4.5.1 (for example, 4.5, 4.4, 4.3, etc.)
-
Check if hg serve process is activeRun `ps aux | grep 'hg serve'` or `pgrep -a hg` to see if the Mercurial protocol server is runningAffected if The protocol server process (hg serve) is currently running and accessible over the network
-
Check for hg serve systemd serviceRun `systemctl list-units | grep hg` or check for services running on port 8000 (common default for hg serve) using `netstat -tlnp | grep 8000` or `ss -tlnp | grep 8000`Affected if A Mercurial protocol server service is enabled or configured to start automatically
-
Verify Debian package version if applicableOn Debian systems, run `dpkg -l | grep mercurial` to see the installed package versionAffected if The installed package version is earlier than 4.5.1-1 (or the equivalent for the distribution)
You are affected if Mercurial version is earlier than 4.5.1 AND the protocol server (hg serve) is exposed to network access, either actively running or configured to run.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.5.1
Upgrade Mercurial to version 4.5.1 or later to remediate this access control vulnerability.
Mercurial 4.5.1 or later
- Check current Mercurial version with `hg --version`
- Upgrade Mercurial to version 4.5.1 or later using your package manager or pip (e.g., `pip install --upgrade mercurial` or `apt-get install mercurial` on Debian)
- Verify the upgrade was successful by running `hg --version` and confirming the version is 4.5.1 or newer
- If running Mercurial as a protocol server, restart the service to ensure the patched version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000132 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data