Description
The software stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
Access Control, Confidentiality: Bypass Protection Mechanism, Read Application Data
An attacker may be able to decrypt the data using brute force attacks.
Potential Mitigations
Phase: Architecture and Design
Description:
Use an encryption scheme that is currently considered to be strong by experts in the field.
CVE References
- CVE-2001-1546
- Weak encryption
- CVE-2004-2172
- Weak encryption (chosen plaintext attack)
- CVE-2002-1682
- Weak encryption
- CVE-2002-1697
- Weak encryption produces same ciphertext from the same plaintext blocks.
- CVE-2002-1739
- Weak encryption
- CVE-2005-2281
- Weak encryption scheme
- CVE-2002-1872
- Weak encryption (XOR)
- CVE-2002-1910
- Weak encryption (reversible algorithm).
- CVE-2002-1946
- Weak encryption (one-to-one mapping).
- CVE-2002-1975
- Encryption error uses fixed salt, simplifying brute force / dictionary attacks (overlaps randomness).
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...