Elastic Kibana up to 8.17.2 File Upload prototype pollution

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Elastic Kibana up to 8.17.2. This affects an unknown function of the component File Upload Handler. The manipulation leads to prototype pollution. This vulnerability is documented as CVE-2025-25015. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Elastic Kibana up to 8.17.2. It has been rated as very critical. This issue affects an unknown functionality of the component File Upload Handler. The manipulation with an unknown input leads to a prototype pollution vulnerability. Using CWE to declare the problem leads to CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP requests. In Kibana versions >= 8.15.0 and < 8.17.1, this is exploitable by users with the Viewer role. In Kibana versions 8.17.1 and 8.17.2 , this is only exploitable by users that have roles that contain all the following privileges: fleet-all, integrations-all, actions:execute-advanced-connectors

It is possible to read the advisory at discuss.elastic.co. The identification of this vulnerability is CVE-2025-25015 since 01/31/2025. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/02/2025). The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

Upgrading to version 8.17.3 eliminates this vulnerability. The upgrade is hosted for download at discuss.elastic.co.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.4
VulDB Meta Temp Score: 9.1

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 9.9
CNA Vector (elastic): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Prototype pollution
CWE: CWE-1321 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kibana 8.17.3

Timelineinfo

01/31/2025 🔍
03/05/2025 +33 days 🔍
03/05/2025 +0 days 🔍
10/02/2025 +211 days 🔍

Sourcesinfo

Advisory: discuss.elastic.co
Status: Confirmed

CVE: CVE-2025-25015 (🔍)
GCVE (CVE): GCVE-0-2025-25015
GCVE (VulDB): GCVE-100-298691

Entryinfo

Created: 03/05/2025 11:48
Updated: 10/02/2025 21:43
Changes: 03/05/2025 11:48 (64), 10/02/2025 21:43 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

 Anonymous User (+0)
1 Year ago
Hello,
I noticed that CVE-2025-25012 and CVE-2025-25015 both describe the same critical vulnerability in Kibana, allowing arbitrary code execution via prototype pollution. However, only CVE-2025-25012 is officially documented and resolved by Elastic Kibana. CVE-2025-25015 is published by NIST but not mentioned in Kibana's security bulletins. Could you clarify this discrepancy?
Thank you.
TEAM CERT
 VulDB Community Team1 Year ago
CVE-2025-25012 is not yet published to the CVE stream but mentioned in the vendor advisory ESA-2025-06. We have published it in VDB-298769. CVE-2025-25015 is maintained by Elastic and the CVE published already but surprisingly not mentioned in the vendor advisory. We don't know the reason for that. This might be a mistake by the Elastic Team. We assume both findings are valid.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!