graphql-engine up to 1.0.0-beta.2 JWT input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in graphql-engine up to 1.0.0-beta.2. This affects an unknown part of the component JWT Handler. Such manipulation leads to input validation. This vulnerability is uniquely identified as CVE-2019-1020015. The attack can be launched remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability was found in graphql-engine up to 1.0.0-beta.2. It has been rated as critical. Affected by this issue is an unknown part of the component JWT Handler. 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 integrity. CVE summarizes:
graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying JWT.
The weakness was disclosed 07/29/2019. This vulnerability is handled as CVE-2019-1020015 since 07/26/2019. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 1.0.0-beta.3 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
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
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: graphql-engine 1.0.0-beta.3
Patch: github.com
Timeline
07/26/2019 🔍07/29/2019 🔍
07/30/2019 🔍
11/13/2023 🔍
Sources
Advisory: f2f14e727b051e3003ba44b9b63eab8186b291acStatus: Not defined
CVE: CVE-2019-1020015 (🔍)
GCVE (CVE): GCVE-0-2019-1020015
GCVE (VulDB): GCVE-100-138932
Entry
Created: 07/30/2019 08:25Updated: 11/13/2023 15:53
Changes: 07/30/2019 08:25 (36), 07/15/2020 09:39 (17), 11/13/2023 15:53 (6)
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.