KibanaApplication · Elastic
CVE-2016-10365
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 · uneditedKibana versions before 4.6.3 and 5.0.1 have an open redirect vulnerability that would enable an attacker to craft a link in the Kibana domain that redirects to an arbitrary website.
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 confidenceKibana versions before 4.6.3 and 5.0.1 contain an open redirect vulnerability in their web interface. Attackers can craft malicious URLs hosted on the Kibana domain that transparently redirect users to arbitrary external websites, enabling phishing and credential theft attacks.
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
KibanaApplication
<= 4.6.2<= 5.0.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.
-
Identify installed Kibana versionCheck the version file in the Kibana installation directory, or query the Kibana API endpoint /api/status, or run 'kibana --version' if availableAffected if The version is 4.6.2 or lower, or 5.0.0 or lower
-
Verify Kibana web interface is accessibleConfirm that the Kibana web interface is reachable over HTTP/HTTPS from users or attackersAffected if The web interface is exposed and accepts user traffic
-
Check for unvalidated redirect parameters in URLsInspect HTTP requests for query parameters that control redirection (such as 'url', 'redirect', or 'returnTo' parameters) being passed to KibanaAffected if The application accepts redirect parameters in URLs without validating that the target is internal
-
Test for open redirect behaviorSend a crafted request to Kibana with a redirect parameter pointing to an external domain (for example, ?next=//attacker.com) and observe if a 302 redirect to the external domain occursAffected if Kibana returns a 302 redirect to an external domain outside of its own control
If the installed Kibana version is 4.6.2 or lower, or 5.0.0 or lower, and the web interface is accessible, the environment is likely affected by this open redirect vulnerability.
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 Kibana to version 4.6.3 or later, or 5.0.1 or later. Alternatively, implement URL validation at the reverse proxy or application level to reject redirect parameters pointing to external domains.
Fix this in Kibana
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10365 — 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-2016-10365 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