| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in AWS S3 Crypto SDK. Impacted is an unknown function. This manipulation of the argument metadata causes weak hash. This vulnerability is registered as CVE-2022-2582. 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 was found in AWS S3 Crypto SDK (affected version not known). It has been declared as problematic. Affected by this vulnerability is some unknown functionality. The manipulation of the argument metadata with an unknown input leads to a weak hash vulnerability. The CWE definition for the vulnerability is CWE-328. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). As an impact it is known to affect confidentiality. The summary by CVE is:
The AWS S3 Crypto SDK sends an unencrypted hash of the plaintext alongside the ciphertext as a metadata field. This hash can be used to brute force the plaintext, if the hash is readable to the attacker. AWS now blocks this metadata field, but older SDK versions still send it.
The weakness was published 12/28/2022 as 35fa6ddf45c061e0f08d3a3b5119f8f4da38f6d1. The advisory is shared at github.com. This vulnerability is known as CVE-2022-2582 since 07/29/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
Applying the patch 35fa6ddf45c061e0f08d3a3b5119f8f4da38f6d1 is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.9
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: 🔍
Exploiting
Class: Weak hashCWE: CWE-328 / CWE-327 / CWE-310
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: 35fa6ddf45c061e0f08d3a3b5119f8f4da38f6d1
Timeline
07/29/2022 🔍12/28/2022 🔍
12/28/2022 🔍
04/11/2025 🔍
Sources
Advisory: 35fa6ddf45c061e0f08d3a3b5119f8f4da38f6d1Status: Confirmed
CVE: CVE-2022-2582 (🔍)
GCVE (CVE): GCVE-0-2022-2582
GCVE (VulDB): GCVE-100-216925
Entry
Created: 12/28/2022 09:16Updated: 04/11/2025 19:42
Changes: 12/28/2022 09:16 (41), 01/25/2023 11:57 (11), 04/11/2025 19:42 (16)
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.