| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Samsung Galaxy S22 and classified as critical. Affected by this vulnerability is an unknown functionality of the component StrongBox. Performing a manipulation results in unusual condition. This vulnerability is reported as CVE-2022-28793. The attack requires a local approach. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in Samsung Galaxy S22 (Smartphone Operating System) (the affected version unknown). This affects an unknown part of the component StrongBox. The manipulation with an unknown input leads to a unusual condition vulnerability. CWE is classifying the issue as CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 05/04/2022. The advisory is shared at security.samsungmobile.com. This vulnerability is uniquely identified as CVE-2022-28793 since 04/07/2022. Neither technical details nor an exploit are publicly available.
Applying a patch 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
Type
Vendor
Name
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.4
VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.4
CNA Vector (Samsung Mobile): 🔍
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: Unusual conditionCWE: CWE-754
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 🔍
Timeline
04/07/2022 🔍05/04/2022 🔍
05/04/2022 🔍
05/07/2022 🔍
Sources
Vendor: samsung.comAdvisory: security.samsungmobile.com
Status: Confirmed
CVE: CVE-2022-28793 (🔍)
GCVE (CVE): GCVE-0-2022-28793
GCVE (VulDB): GCVE-100-198957
Entry
Created: 05/04/2022 06:45Updated: 05/07/2022 08:41
Changes: 05/04/2022 06:45 (47), 05/07/2022 08:41 (1)
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.