dbcve.org
H2oApplication · Dena

CVE-2017-10872

MEDIUM · 6.5 CVSS v3.0 Published 2017-12-22
Fix available
A fix is available. Upgrade to after 2.2.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
H2O version 2.2.3 and earlier allows remote attackers to cause a denial of service in the server via unspecified vectors.

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 confidence

H2O versions 2.2.3 and earlier contain a vulnerability allowing remote unauthenticated attackers to cause denial of service via unspecified vectors. The CVSS 6.5 indicates a network-exploitable DoS with low attack complexity and no user interaction required.

MitigationUpgrade H2O to a version newer than 2.2.3. Test the upgrade in a staging environment before production deployment to ensure compatibility with existing configurations and applications.

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
H2oApplication
Affected:<= 2.2.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify H2O is installed
    Check for the H2O binary or service on the system. Common locations include /usr/sbin/h2o, /usr/bin/h2o, or check system services (systemctl list-units | grep h2o or ps aux | grep h2o).
    Affected if H2O server software is present on the system
  2. Determine installed H2O version
    Run 'h2o --version' or 'h2o -v' from the command line. If installed as a service, also check package manager listings (dpkg -l | grep h2o, rpm -qa | grep h2o, or brew list h2o).
    Affected if The version command fails or returns a version number
  3. Compare version to affected range
    Review the version output against the affected range: versions 2.2.3 and earlier are vulnerable. Note that versions after 2.2.3 are fixed.
    Affected if The installed version is 2.2.3 or any earlier version (e.g., 2.2.2, 2.2.1, 2.2.0, etc.)
  4. Confirm H2O service is running
    Check if the H2O process is active: systemctl status h2o, service h2o status, or ps aux | grep h2o. The vulnerability is a DoS against a running server.
    Affected if H2O service is currently running and accepts network connections

A system is affected if H2O server is installed and the running version is 2.2.3 or any earlier version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 2.2.3
Interim mitigation

Upgrade H2O to a version newer than 2.2.3. Test the upgrade in a staging environment before production deployment to ensure compatibility with existing configurations and applications.

Fix this in H2o Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-10872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-10872 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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