OpenShift OSIN ClientSecretMatches/CheckClientSecret secret timing discrepancy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenShift OSIN. Affected by this issue is the function ClientSecretMatches/CheckClientSecret. Performing a manipulation of the argument secret results in timing discrepancy.
This vulnerability is reported as CVE-2021-4294. No exploit exists.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in OpenShift OSIN (Virtualization Software) (affected version unknown). It has been classified as problematic. This affects the function ClientSecretMatches/CheckClientSecret. The manipulation of the argument secret with an unknown input leads to a timing discrepancy vulnerability. CWE is classifying the issue as CWE-208. Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not. This is going to have an impact on confidentiality.
The weakness was disclosed 12/28/2022 as 200. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2021-4294. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Applying the patch 8612686d6dda34ae9ef6b5a974e4b7accb4fea29 is able to eliminate this problem. The bugfix is ready for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Product: https://github.com/openshift/osin/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.6VulDB Meta Temp Score: 2.4
VulDB Base Score: 2.6
VulDB Temp Score: 2.4
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: Timing discrepancyCWE: CWE-208 / CWE-203 / CWE-200
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 8612686d6dda34ae9ef6b5a974e4b7accb4fea29
Timeline
12/28/2022 🔍12/28/2022 🔍
12/28/2022 🔍
01/25/2023 🔍
Sources
Product: github.comAdvisory: 200
Status: Not defined
CVE: CVE-2021-4294 (🔍)
GCVE (CVE): GCVE-0-2021-4294
GCVE (VulDB): GCVE-100-216987
Entry
Created: 12/28/2022 17:56Updated: 01/25/2023 23:15
Changes: 12/28/2022 17:56 (42), 01/25/2023 23:15 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.