KibanaApplication · Elastic
CVE-2022-38779
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 open redirect issue was discovered in Kibana that could lead to a user being redirected to an arbitrary website if they use a maliciously crafted Kibana URL.
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 confidenceAn open redirect vulnerability in Kibana allows attackers to craft malicious URLs that can redirect users to arbitrary external websites. This occurs because the application insufficiently validates redirect destination parameters, enabling phishing attacks where users believe they are visiting a legitimate Kibana URL.
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
>= 7.0.0, < 7.17.9>= 8.0.0, < 8.6.2CVSS 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.1/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 Kibana version by accessing the status page (typically /api/status) or checking the Kibana banner/footer in the web UIAffected if The displayed version falls within >= 7.0.0 and < 7.17.9, OR >= 8.0.0 and < 8.6.2
-
Verify Kibana is accessible over networkConfirm the Kibana web interface is reachable (port 5601 by default)Affected if Kibana is exposed and the version is in the affected range, making the open redirect exploitable
-
Check for suspicious redirect patternsReview Kibana access logs for requests containing suspicious redirect parameters (such as ?next=, ?return_to=, or similar redirect indicators pointing to external domains)Affected if Logs show redirect parameters with external URLs that do not belong to the organization's domain
A user is affected if their installed Kibana version is 7.0.0 through 7.17.x or 8.0.0 through 8.6.1, and the Kibana interface is accessible to potential attackers.
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.
dbcve · scoped7.17.98.6.2
Apply the appropriate Kibana security patch or update to a version that addresses CVE-2022-38779, which implements proper validation of redirect URLs to prevent arbitrary external redirects.
Kibana 7.17.9 (for 7.x) or 8.6.2 (for 8.x)
- 1. Determine your current Kibana version by checking the KibanaAbout page or running `bin/kibana --version`
- 2. For Kibana 7.x users: Plan to upgrade to version 7.17.9 or later
- 3. For Kibana 8.x users: Plan to upgrade to version 8.6.2 or later
- 4. Review the Elasticsearch and Kibana upgrade guide at https://www.elastic.co/guide/en/kibana/current/upgrade.html
- 5. Create a backup of your Kibana configuration and saved objects
- 6. Test the upgrade in a non-production environment first
- 7. Perform the upgrade following the standard rolling upgrade or full cluster restart procedure
- 8. Verify that Kibana starts successfully and the version number matches the expected fixed version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Kibana
Scoped from the published advisory
- 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-2022-38779 — 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-2022-38779 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