Pivotal Greenplum Command Center up to 2.5.0 Blind sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Pivotal Greenplum Command Center up to 2.5.0. The impacted element is an unknown function. The manipulation leads to sql injection (Blind). This vulnerability is documented as CVE-2018-1280. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Pivotal Greenplum Command Center up to 2.5.0. This issue affects some unknown processing. The manipulation with an unknown input leads to a sql injection vulnerability (Blind). Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Pivotal Greenplum Command Center versions 2.x prior to 2.5.1 contains a blind SQL injection vulnerability. An unauthenticated user can perform a SQL injection in the command center which results in disclosure of database contents.
The bug was discovered 05/07/2018. The weakness was released 05/11/2018 by Matt (Website). The advisory is shared at pivotal.io. The identification of this vulnerability is CVE-2018-1280 since 12/06/2017. The attack may be initiated remotely. Required for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.5.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 104153†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://pivotal.io/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: BlindClass: Sql injection / Blind
CWE: CWE-89 / CWE-74 / CWE-707
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: Greenplum Command Center 2.5.1
Timeline
12/06/2017 🔍05/07/2018 🔍
05/11/2018 🔍
05/11/2018 🔍
05/12/2018 🔍
05/14/2018 🔍
02/04/2020 🔍
Sources
Vendor: pivotal.ioAdvisory: pivotal.io
Researcher: Matt
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-1280 (🔍)
GCVE (CVE): GCVE-0-2018-1280
GCVE (VulDB): GCVE-100-117641
SecurityFocus: 104153 - Pivotal Greenplum Command Center CVE-2018-1280 SQL Injection Vulnerability
Entry
Created: 05/12/2018 08:50Updated: 02/04/2020 15:55
Changes: 05/12/2018 08:50 (60), 02/04/2020 15:55 (5)
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.