Vulnerability from bitnami_vulndb
Published
2025-12-20 11:36
Modified
2025-12-20 12:06
Summary
Kibana Allocation of Resources Without Limits or Throttling
Details
Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) of computing resources and a denial of service (DoS) of the Kibana process via a crafted HTTP request.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "elk",
"purl": "pkg:bitnami/elk"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.19.9"
},
{
"introduced": "9.0.0"
},
{
"fixed": "9.1.9"
},
{
"introduced": "9.2.0"
},
{
"fixed": "9.2.3"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2025-68389"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:elasticsearch:kibana:*:*:*:*:*:node.js:*:*"
],
"severity": "Medium"
},
"details": "Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can allow a low-privileged authenticated user to cause Excessive Allocation (CAPEC-130) of computing resources and a denial of service (DoS) of the Kibana process via a crafted HTTP request.",
"id": "BIT-elk-2025-68389",
"modified": "2025-12-20T12:06:39.262Z",
"published": "2025-12-20T11:36:40.368Z",
"references": [
{
"type": "WEB",
"url": "https://discuss.elastic.co/t/kibana-8-19-9-9-1-9-and-9-2-3-security-update-esa-2025-36/384184"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68389"
}
],
"schema_version": "1.6.2",
"summary": "Kibana Allocation of Resources Without Limits or Throttling"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…