Juniper Contrail Service Orchestration up to 6.1.0 Patch 2 REST API protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Juniper Contrail Service Orchestration up to 6.1.0 Patch 2. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component REST API. The manipulation leads to protection mechanism. This vulnerability is referenced as CVE-2022-22152. Remote exploitation of the attack is possible. No exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, has been found in Juniper Contrail Service Orchestration up to 6.1.0 Patch 2. This issue affects an unknown code block of the component REST API. The manipulation with an unknown input leads to a protection mechanism vulnerability. Using CWE to declare the problem leads to CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. Impacted is confidentiality.
The weakness was published 01/19/2022 as JSA11260. The advisory is shared at kb.juniper.net. The identification of this vulnerability is CVE-2022-22152 since 12/21/2021. Neither technical details nor an exploit are publicly available.
Applying the patch 6.1.0 Patch 3 is able to eliminate this problem.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.juniper.net/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.7
CNA Vector (Juniper Networks, Inc.): 🔍
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: Protection mechanismCWE: CWE-693
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 6.1.0 Patch 3
Timeline
12/21/2021 🔍01/19/2022 🔍
01/19/2022 🔍
01/20/2022 🔍
Sources
Vendor: juniper.netAdvisory: JSA11260
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-22152 (🔍)
GCVE (CVE): GCVE-0-2022-22152
GCVE (VulDB): GCVE-100-190685
Entry
Created: 01/19/2022 10:02Updated: 01/20/2022 13:47
Changes: 01/19/2022 10:02 (50), 01/20/2022 13:47 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.