Zenoss 2.3.0/2.3.3/2.4.0/2.4.2/2.4.5 getJSONEventsInfo sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.0 | $0-$5k | 0.00 |
A vulnerability was found in Zenoss 2.3.0/2.3.3/2.4.0/2.4.2/2.4.5. It has been declared as critical. This vulnerability affects an unknown function of the file zport/dmd/Events/getJSONEventsInfo. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Multiple SQL injection vulnerabilities in zport/dmd/Events/getJSONEventsInfo in Zenoss 2.3.3, and other versions before 2.5, allow remote authenticated users to execute arbitrary SQL commands via the (1) severity, (2) state, (3) filter, (4) offset, and (5) count parameters.
The bug was discovered 03/10/2009. The weakness was disclosed 01/14/2010 (Website). The advisory is available at securityfocus.com. This vulnerability was named CVE-2010-0712 since 02/26/2010. The exploitation appears to be easy. The attack can be initiated remotely. The successful exploitation requires a single authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 310 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.3.0 eliminates this vulnerability. A possible mitigation has been published 1 days after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at X-Force (55670). The entry 51983 is pretty similar.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
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 |
OpenVAS ID: 800990
OpenVAS Name: Zenoss Server Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Zenoss 2.3.0
Timeline
03/10/2009 🔍01/14/2010 🔍
01/14/2010 🔍
01/15/2010 🔍
01/18/2010 🔍
01/18/2010 🔍
02/26/2010 🔍
02/26/2010 🔍
03/18/2015 🔍
09/02/2021 🔍
Sources
Advisory: 15257⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2010-0712 (🔍)
X-Force: 55670
SecurityFocus: 37802 - Zenoss Multiple SQL Injection Vulnerabilities
Secunia: 38195 - Zenoss Core SQL Injection and Cross-Site Request Forgery Vulnerabilities, Less Critical
OSVDB: 61804 - Zenoss Core zport/dmd/Events/getJSONEventsInfo Multiple Parameter SQL Injection
See also: 🔍
Entry
Created: 03/18/2015 15:15Updated: 09/02/2021 19:13
Changes: 03/18/2015 15:15 (57), 09/03/2017 13:44 (13), 09/02/2021 19:13 (3)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.