Pivotal PCF Elastic Runtime up to 1.6.59/1.7.40/1.8.22/1.9.0 JSON Web Token Library input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pivotal PCF Elastic Runtime up to 1.6.59/1.7.40/1.8.22/1.9.0 and classified as critical. This issue affects some unknown processing of the component JSON Web Token Library. Such manipulation leads to input validation. This vulnerability is referenced as CVE-2017-2773. It is possible to launch the attack remotely. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Pivotal PCF Elastic Runtime up to 1.6.59/1.7.40/1.8.22/1.9.0. Affected by this issue is an unknown code of the component JSON Web Token Library. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in Pivotal PCF Elastic Runtime 1.6.x versions prior to 1.6.60, 1.7.x versions prior to 1.7.41, 1.8.x versions prior to 1.8.23, and 1.9.x versions prior to 1.9.1. Incomplete validation logic in JSON Web Token (JWT) libraries can allow unprivileged attackers to impersonate other users in multiple components included in PCF Elastic Runtime, aka an "Unauthenticated JWT signing algorithm in multiple components" issue.
The bug was discovered 03/27/2017. The weakness was published 06/13/2017 (Website). The advisory is shared for download at pivotal.io. This vulnerability is handled as CVE-2017-2773 since 12/01/2016. The attack may be launched remotely. A simple authentication is needed for exploitation. There are neither technical details nor an exploit publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 78 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.6.60, 1.7.41, 1.8.23 or 1.9.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 97135†). Similar entries are available at VDB-102262 and VDB-102261. Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 1.0
- 1.1
- 1.2
- 1.3
- 1.4
- 1.5
- 1.6
- 1.6.0
- 1.6.1
- 1.6.2
- 1.6.3
- 1.6.4
- 1.6.5
- 1.6.6
- 1.6.7
- 1.6.8
- 1.6.9
- 1.6.10
- 1.6.11
- 1.6.12
- 1.6.13
- 1.6.14
- 1.6.15
- 1.6.16
- 1.6.17
- 1.6.18
- 1.6.19
- 1.6.20
- 1.6.21
- 1.6.22
- 1.6.23
- 1.6.24
- 1.6.25
- 1.6.26
- 1.6.27
- 1.6.28
- 1.6.29
- 1.6.30
- 1.6.31
- 1.6.32
- 1.6.33
- 1.6.34
- 1.6.35
- 1.6.36
- 1.6.37
- 1.6.38
- 1.6.39
- 1.6.40
- 1.6.41
- 1.6.42
- 1.6.43
- 1.6.44
- 1.6.45
- 1.6.46
- 1.6.47
- 1.6.48
- 1.6.49
- 1.6.50
- 1.6.51
- 1.6.52
- 1.6.53
- 1.6.54
- 1.6.55
- 1.6.56
- 1.6.57
- 1.6.58
- 1.6.59
- 1.7
- 1.7.0
- 1.7.1
- 1.7.2
- 1.7.3
- 1.7.4
- 1.7.5
- 1.7.6
- 1.7.7
- 1.7.8
- 1.7.9
- 1.7.10
- 1.7.11
- 1.7.12
- 1.7.13
- 1.7.14
- 1.7.15
- 1.7.16
- 1.7.17
- 1.7.18
- 1.7.19
- 1.7.20
- 1.7.21
- 1.7.22
- 1.7.23
- 1.7.24
- 1.7.25
- 1.7.26
- 1.7.27
- 1.7.28
- 1.7.29
- 1.7.30
- 1.7.31
- 1.7.32
- 1.7.33
- 1.7.34
- 1.7.35
- 1.7.36
- 1.7.37
- 1.7.38
- 1.7.39
- 1.7.40
- 1.8
- 1.8.0
- 1.8.1
- 1.8.2
- 1.8.3
- 1.8.4
- 1.8.5
- 1.8.6
- 1.8.7
- 1.8.8
- 1.8.9
- 1.8.10
- 1.8.11
- 1.8.12
- 1.8.13
- 1.8.14
- 1.8.15
- 1.8.16
- 1.8.17
- 1.8.18
- 1.8.19
- 1.8.20
- 1.8.21
- 1.8.22
- 1.9.0
License
Website
- Vendor: https://pivotal.io/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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
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: PCF Elastic Runtime 1.6.60/1.7.41/1.8.23/1.9.1
Timeline
12/01/2016 🔍03/27/2017 🔍
03/27/2017 🔍
06/13/2017 🔍
06/13/2017 🔍
06/13/2017 🔍
10/16/2019 🔍
Sources
Vendor: pivotal.ioAdvisory: pivotal.io
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-2773 (🔍)
GCVE (CVE): GCVE-0-2017-2773
GCVE (VulDB): GCVE-100-102260
SecurityFocus: 97135 - Pivotal Cloud Foundry Elastic Runtime CVE-2017-2773 Security Bypass Vulnerability
See also: 🔍
Entry
Created: 06/13/2017 16:59Updated: 10/16/2019 11:38
Changes: 06/13/2017 16:59 (63), 10/16/2019 11:38 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.