Zalando Skipper prior 0.13.218 Request access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Zalando Skipper. This affects an unknown function of the component Request Handler. Such manipulation leads to access control. This vulnerability is uniquely identified as CVE-2022-34296. The attack can only be initiated within the local network. No exploit exists. The affected component should be upgraded.
Details
A vulnerability was found in Zalando Skipper. It has been rated as critical. Affected by this issue is an unknown part of the component Request Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In Zalando Skipper before 0.13.218, a query predicate could be bypassed via a prepared request.
The weakness was disclosed 06/24/2022. The advisory is available at github.com. This vulnerability is handled as CVE-2022-34296 since 06/22/2022. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
Upgrading to version 0.13.218 eliminates this vulnerability. The upgrade is hosted for download at github.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Website
- Product: https://github.com/zalando/skipper/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: Skipper 0.13.218
Timeline
06/22/2022 🔍06/24/2022 🔍
06/24/2022 🔍
06/24/2022 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2022-34296 (🔍)
GCVE (CVE): GCVE-0-2022-34296
GCVE (VulDB): GCVE-100-202562
Entry
Created: 06/24/2022 07:08Changes: 06/24/2022 07:08 (40)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.