ThriftApplication · Apache
CVE-2018-11798
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 · uneditedThe Apache Thrift Node.js static web server in versions 0.9.2 through 0.11.0 have been determined to contain a security vulnerability in which a remote user has the ability to access files outside the set webservers docroot path.
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 confidenceApache Thrift's Node.js static web server versions 0.9.2 through 0.11.0 contain a path traversal vulnerability allowing remote attackers to access files outside the configured document root via '..' sequences in HTTP requests.
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
ThriftApplication
>= 0.9.2, <= 0.11.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 if Apache Thrift Node.js static web server is in useReview your application dependencies and codebase for references to the Apache Thrift Node.js library, particularly the static web server component (often imported as thrift or similar Node modules). Check package.json, node_modules, or any server initialization code that loads Thrift's web server functionality.Affected if The Node.js static web server from Apache Thrift is deployed as part of your application stack.
-
Determine the installed Apache Thrift versionRun 'npm list thrift' or check your package-lock.json/package.json for the @thrift or thrift npm package version number. If using a bundled distribution, locate the Thrift library files and check the version string in the package metadata.Affected if The installed version falls within >= 0.9.2 and <= 0.11.0.
-
Verify the static web server feature is enabledInspect your server initialization code to confirm the Thrift static web server is actually started and serving HTTP requests. Look for code that initializes TStaticServer, static server, or similar Thrift server components that serve static content.Affected if The static web server component is actively running and handling HTTP requests.
-
Test for path traversal vulnerability (optional confirmation)Send a curl request with '..' sequences to your Thrift static web server endpoint, such as: curl 'http://<server>/..%2F..%2Fetc/passwd' or curl 'http://<server>/../some/file'. Check if the server returns files from outside the intended document root.Affected if The server returns files from outside the configured document root directory.
You are affected if you are running Apache Thrift Node.js static web server version 0.9.2 through 0.11.0 and the static web server feature is actively serving HTTP requests.
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 to Apache Thrift version 0.11.0 or later where the vulnerability is patched, or implement web server-level path validation to block traversal sequences.
Fix this in Thrift
Scoped from the published advisory
- Consultation3.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11798 — 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-11798 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