HTTPS Compressed Data Breach missing cryptographic step
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HTTPS. It has been rated as problematic. This vulnerability affects unknown code of the component Compressed Data Handler. This manipulation causes missing cryptographic step. This vulnerability is tracked as CVE-2013-3587. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in HTTPS (version unknown). Affected by this vulnerability is an unknown function of the component Compressed Data Handler. The manipulation with an unknown input leads to a missing cryptographic step vulnerability. The CWE definition for the vulnerability is CWE-325. The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm. As an impact it is known to affect confidentiality.
The weakness was disclosed 08/14/2023. This vulnerability is known as CVE-2013-3587. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Missing cryptographic stepCWE: CWE-325
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/21/2013 🔍08/14/2023 🔍
08/14/2023 🔍
09/09/2023 🔍
Sources
Status: Not definedCVE: CVE-2013-3587 (🔍)
GCVE (CVE): GCVE-0-2013-3587
GCVE (VulDB): GCVE-100-237097
Entry
Created: 08/14/2023 21:00Updated: 09/09/2023 07:41
Changes: 08/14/2023 21:00 (34), 08/14/2023 21:01 (1), 09/09/2023 07:35 (2), 09/09/2023 07:41 (18)
Complete: 🔍
Cache ID: 216:BE0:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.