Apache Zeppelin up to 0.11.x JDBC URL Validation input validation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Apache Zeppelin up to 0.11.x. It has been rated as problematic. The impacted element is an unknown function of the component JDBC URL Validation Handler. Performing a manipulation results in input validation. This vulnerability was named CVE-2024-52279. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in Apache Zeppelin up to 0.11.x. It has been classified as problematic. This affects an unknown function of the component JDBC URL Validation Handler. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. The impact remains unknown. The summary by CVE is:
Improper Input Validation vulnerability in Apache Zeppelin. The fix for JDBC URL validation in CVE-2024-31864 did not account for URL encoded input. This issue affects Apache Zeppelin: from 0.11.1 before 0.12.0. Users are recommended to upgrade to version 0.12.0, which fixes the issue.
The weakness was presented by H Ming. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-52279 since 11/06/2024. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/06/2025).
Upgrading to version 0.12.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-54846). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
- Product: https://github.com/apache/zeppelin/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Zeppelin 0.12.0
Patch: github.com
Timeline
11/06/2024 CVE reserved08/03/2025 Advisory disclosed
08/03/2025 VulDB entry created
08/06/2025 VulDB entry last update
Sources
Vendor: apache.orgProduct: github.com
Advisory: github.com
Researcher: H Ming
Status: Confirmed
CVE: CVE-2024-52279 (🔒)
GCVE (CVE): GCVE-0-2024-52279
GCVE (VulDB): GCVE-100-318633
EUVD: 🔒
Entry
Created: 08/03/2025 14:33Updated: 08/06/2025 04:24
Changes: 08/03/2025 14:33 (56), 08/03/2025 18:36 (1), 08/05/2025 18:47 (1), 08/06/2025 04:24 (10)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.