CVE-2018-13003
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 · uneditedAn issue was discovered in OpenTSDB 2.3.0. There is XSS in parameter 'type' to the /suggest URI.
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 confidenceOpenTSDB 2.3.0 contains a reflected Cross-Site Scripting (XSS) vulnerability in the /suggest URI endpoint. The 'type' parameter is not properly sanitized or encoded before being reflected back in the HTTP response, allowing an attacker to inject malicious JavaScript code that executes in the context of 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= 2.3.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Confirm OpenTSDB installation and versionLocate the OpenTSDB installation directory and check for version information. Common locations include: a version file in the installation root, the GUI footer, or running 'tsdb version' if the CLI is available. Also check any package manager records if installed via yum/apt.Affected if The installed version is exactly 2.3.0
-
Verify HTTP service is runningCheck if the OpenTSDB HTTP service is active and listening on its port (default 4242). Use commands like 'netstat -tlnp | grep 4242' or 'curl http://localhost:4242' to confirm the service is accessible.Affected if The HTTP service is running and accessible (required for the XSS to be exploitable)
-
Identify if /suggest endpoint is exposedSend a request to the /suggest endpoint, for example: curl 'http://<host>:4242/suggest?type=metrics'. Check if the endpoint returns a response.Affected if The /suggest endpoint is accessible and responds to requests
-
Test for parameter reflection in responseSend a request with a test value in the 'type' parameter, such as: curl 'http://<host>:4242/suggest?type=testvalue'. Examine the HTTP response body to see if the 'type' parameter value is reflected back without encoding.Affected if The 'type' parameter value appears in the response body without HTML encoding (e.g., visible as plain text rather than being escaped)
-
Compare against affected version rangeVerify that your OpenTSDB version is 2.3.0. Check version files, the web interface, or query the API if a version endpoint exists.Affected if The installed version is exactly 2.3.0
You are affected if OpenTSDB version 2.3.0 is installed, the HTTP service is running, and the /suggest endpoint reflects the 'type' parameter back to the user without proper encoding.
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 dataImplement proper input validation and output encoding for the 'type' parameter in the /suggest endpoint. Alternatively, upgrade to a patched version of OpenTSDB if available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13003 — 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-13003 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