Seafile up to 6.2.11 Cipher Block Chaining Mode Initialization Vector inadequate encryption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.5 | $0-$5k | 0.00 |
A vulnerability was found in Seafile up to 6.2.11 and classified as critical. This issue affects some unknown functionality of the component Cipher Block Chaining Mode. The manipulation with an unknown input leads to a inadequate encryption vulnerability (Initialization Vector). Using CWE to declare the problem leads to CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Seafile through 6.2.11 always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks.
The bug was discovered 09/03/2013. The weakness was presented 02/21/2019. The identification of this vulnerability is CVE-2013-7469 since 02/17/2019. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 1997 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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
Name: Initialization VectorClass: Inadequate encryption / Initialization Vector
CWE: CWE-326 / CWE-310
ATT&CK: T1600
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
09/03/2013 🔍02/17/2019 🔍
02/21/2019 🔍
02/21/2019 🔍
07/11/2023 🔍
Sources
Advisory: 350Status: Not defined
CVE: CVE-2013-7469 (🔍)
Entry
Created: 02/21/2019 09:12Updated: 07/11/2023 16:46
Changes: 02/21/2019 09:12 (54), 05/11/2020 17:51 (1), 07/11/2023 16:46 (4)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.