HTTP ServerWeb server / proxy · Akka
CVE-2017-1000118
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 · uneditedAkka HTTP versions <= 10.0.5 Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service
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 confidenceIn Akka HTTP versions 10.0.5 and earlier, parsing an HTTP Accept header containing an illegal or crafted media range triggers excessive recursive processing in the media type parser, causing a StackOverflowError and resulting in denial of service.
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
HTTP ServerWeb server / proxy
<= 10.0.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Akka HTTP usageSearch your project dependencies (Maven pom.xml, sbt build files, Gradle dependencies) for akka-http-core or akka-http librariesAffected if Akka HTTP library is present in the project dependencies
-
Check Akka HTTP versionReview your dependency management file to determine the exact version of akka-http-core or akka-http libraries. Look for version declarations in your build configurationAffected if The declared version is 10.0.5 or earlier
-
Verify runtime loaded versionAt runtime, inspect the loaded Akka HTTP JAR file name or use code to print the version from the library (e.g., check manifest.mf or use reflection to access version info from the akka.http.Version object if available)Affected if The runtime version resolves to 10.0.5 or earlier
-
Confirm HTTP Accept header processing is enabledVerify your Akka HTTP server routes are configured to handle incoming HTTP requests. The vulnerability triggers when parsing Accept headers from incoming requests, which is enabled by default for any Akka HTTP server handling HTTP trafficAffected if Akka HTTP server is accepting HTTP connections (the Accept header parsing is enabled by default for all HTTP servers)
-
Review request handling logsCheck application logs for StackOverflowError exceptions occurring during HTTP request processing, particularly around media type parsing. Enable debug logging for akka.http.parsing for visibilityAffected if StackOverflowError exceptions appear in logs during Accept header parsing
You are affected if Akka HTTP version 10.0.5 or earlier is in use and your server processes HTTP requests containing Accept headers, as the vulnerable media type parser is invoked by default.
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.
From vendor dataUpgrade Akka HTTP to a version greater than 10.0.5 where the media range parsing logic has been fixed to handle malformed input without recursing infinitely.
Fix this in HTTP Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000118 — 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-2017-1000118 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