CVE-2007-3528
Summary
| CVE | CVE-2007-3528 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2007-07-03 18:30:00 UTC |
| Updated | 2026-04-23 00:35:47 UTC |
| Description | The blowfish mode in DAR before 2.3.4 uses weak Blowfish-CBC cryptography by (1) discarding random bits by the blowfish::make_ivec function in libdar/crypto.cpp that results in predictable and repeating IV values, and (2) direct use of a password for keying, which makes it easier for context-dependent attackers to decrypt files. |
Risk And Classification
Primary CVSS: v2.0 5 from [email protected]
AV:N/AC:L/Au:N/C:P/I:N/A:N
Problem Types: NVD-CWE-Other | n/a
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
LowAuthentication
NoneConfidentiality
PartialIntegrity
NoneAvailability
NoneAV:N/AC:L/Au:N/C:P/I:N/A:N
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| osvdb.org/38189 | af854a3a-2127-422b-91ae-364da2661108 | osvdb.org | |
| #425335 - dar: blowfish encryption weakened by frequent IV collisions - Debian Bug report logs | af854a3a-2127-422b-91ae-364da2661108 | bugs.debian.org | |
| DAR - Disk ARchive / Bugs / #97 blowfish encryption weakened by frequent IV collisions | af854a3a-2127-422b-91ae-364da2661108 | sourceforge.net | |
| Page not found - SourceForge.net | af854a3a-2127-422b-91ae-364da2661108 | sourceforge.net | Patch |
| DAR Blowfish IV Collision Weakness - Secunia.com | af854a3a-2127-422b-91ae-364da2661108 | secunia.com | |
| Page not found - SourceForge.net | af854a3a-2127-422b-91ae-364da2661108 | sourceforge.net | |
| osvdb.org/38190 | af854a3a-2127-422b-91ae-364da2661108 | osvdb.org | |
| Disk ARchive Flawed Blowfish-CBC Cryptography Implementation Weakness | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.