CVE-2024-10086
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 · uneditedA vulnerability was identified in Consul and Consul Enterprise such that the server response did not explicitly set a Content-Type HTTP header, allowing user-provided inputs to be misinterpreted and lead to reflected XSS.
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 · moderate confidenceConsul and Consul Enterprise fail to explicitly set the Content-Type HTTP header in server responses. This allows browsers to interpret responses inconsistently, enabling reflected XSS where malicious scripts are injected via user-provided inputs and executed in the victim's browser.
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>= 1.4.1, < 1.15.15>= 1.4.1, < 1.20.0>= 1.18.0, < 1.18.5>= 1.19.0, < 1.19.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify Consul versionRun 'consul --version' or check the Consul process/service version informationAffected if version falls within < 1.15.15, < 1.20.0, < 1.18.5, or < 1.19.3 for versions >= 1.4.1
-
Verify HTTP API is accessibleSend a request to a Consul HTTP endpoint such as 'curl -I http://localhost:8500/v1/status/leader' or the UI portAffected if Consul HTTP API is reachable on the network
-
Inspect Content-Type header in responsesUse curl or a similar tool to fetch a Consul HTTP response and inspect headers: 'curl -I http://localhost:8500/' and check for absence of Content-Type header or Content-Type not explicitly set to 'text/html' or similar for HTML-returning endpointsAffected if HTTP responses lack explicit Content-Type header (e.g., header is missing or shows generic values)
A user is affected if running a Consul version in the affected ranges AND the Consul HTTP API is accessible without Content-Type headers being set in responses.
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 · scoped1.15.151.18.51.19.3
Configure Consul to explicitly set the Content-Type header (e.g., 'text/html; charset=utf-8') for all HTTP responses that may contain user-controlled content to prevent XSS exploitation.
Consul 1.15.16, 1.18.6, 1.19.4, 1.20.1 or later (select based on current version branch)
- 1. Identify the current Consul version in use by running `consul --version`
- 2. Based on the current version line, upgrade to the corresponding fixed release:
- - For 1.15.x line: upgrade to 1.15.16 or later
- - For 1.18.x line: upgrade to 1.18.6 or later
- - For 1.19.x line: upgrade to 1.19.4 or later
- - For 1.20.x line: upgrade to 1.20.1 or later
- 3. Download the appropriate Consul release from https://www.consul.io/downloads
- 4. Follow the standard Consul upgrade procedure: https://developer.hashicorp.com/consul/docs/upgrading
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10086 — 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-2024-10086 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