KibanaApplication · Elastic
CVE-2024-23442
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 · moderate confidenceKibana contains an open redirect vulnerability where a maliciously crafted URL can cause users to be redirected to an arbitrary external website. This occurs due to insufficient validation of the redirect target in the application.
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.17.22>= 8.0.0, < 8.14.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.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.
-
Find installed Kibana versionRun 'bin/kibana --version' or check the package.json file in the Kibana installation directory, or query the Kibana status API at GET /api/statusAffected if The version returned is less than 7.17.22, or greater than or equal to 8.0.0 but less than 8.14.0
-
Confirm Kibana web interface is exposedVerify that the Kibana server is running and accessible over HTTP/HTTPS to external users or via untrusted linksAffected if Kibana is reachable via a browser or API that could process malicious redirect URLs
-
Review access logs for redirect patternsExamine Kibana server logs (kibana.yml config log file) and proxy logs for requests with suspicious 'redirect' or 'url' parameters pointing to external domains, especially look for patterns like 'http://' or 'https://' in query stringsAffected if Any entries show redirects to unknown external domains originating from Kibana URLs
You are affected if your installed Kibana version falls within < 7.17.22 or >= 8.0.0 to < 8.14.0 AND the Kibana interface is accessible to users who could click maliciously crafted URLs.
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.228.14.0
Apply the vendor-provided patch to Kibana. Users should avoid clicking untrusted Kibana URLs until the patch is applied, as the vulnerability can facilitate phishing attacks.
Kibana 7.17.22 or 8.14.0 (depending on your major version branch)
- Backup your Kibana configuration and any custom dashboards or visualizations
- Stop the Kibana service
- Upgrade Kibana to version 7.17.22 (for 7.x installations) or 8.14.0 (for 8.x installations) using your package manager or binary installation method
- Verify the integrity of the downloaded package using Elasticsearch'sPGP signatures or checksums
- Start the Kibana service
- Verify the upgrade was successful by checking the Kibana health endpoint and logging in
Generated from the published advisory — verify against the referenced sources before acting.
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-2024-23442 — 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-2024-23442 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