KibanaApplication · Elastic
CVE-2022-38778
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 · uneditedA flaw (CVE-2022-38900) was discovered in one of Kibana’s third party dependencies, that could allow an authenticated user to perform a request that crashes the Kibana server process.
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 confidenceCVE-2022-38778 is a denial of service vulnerability in Kibana's third-party dependency. An authenticated user can send a specially crafted request that crashes the Kibana server process, causing service disruption.
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.1< 0.2.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 versionRun 'kibana --version' or check the version in the kibana.yml config file, or look at the package.json in the Kibana installation directoryAffected if version is >= 7.0.0 and < 7.17.9, or >= 8.0.0 and < 8.6.1
-
Check decode-uri-component dependency versionExamine the node_modules/decode-uri-component/package.json file within the Kibana installation, or run 'npm list decode-uri-component' if npm is accessibleAffected if decode-uri-component version is present and less than 0.2.1
-
Confirm Kibana process is runningCheck if the Kibana process is currently active using system commands like 'ps aux | grep kibana' or service status commandsAffected if Kibana is running and meets the vulnerable version criteria above
Your environment is affected if you are running Kibana version 7.0.0 through 7.17.8, or 8.0.0 through 8.6.0, with the decode-uri-component dependency version below 0.2.1.
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 · scoped0.2.17.17.98.6.1
Update Kibana to the latest version that includes the patched dependency. Until then, strictly limit user access to trusted authenticated users only and monitor for unexpected process crashes.
Kibana 7.17.9+ (7.x) or Kibana 8.6.1+ (8.x)
- Upgrade Kibana to version 7.17.9 or later for the 7.x product line
- Upgrade Kibana to version 8.6.1 or later for the 8.x product line
- Restart the Kibana service after upgrading to apply the changes
- Verify that the 'decode-uri-component' dependency has been updated to version 0.2.1 or later
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-38778 — 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-38778 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