Description
The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.
When an application relies on obfuscation or incorrectly applied / weak encryption to protect client-controllable tokens or parameters, that may have an effect on the user state, system state, or some decision made on the server. Without protecting the tokens/parameters for integrity, the application is vulnerable to an attack where an adversary traverses the space of possible values of the said token/parameter in order to attempt to gain an advantage. The goal of the attacker is to find another admissible value that will somehow elevate their privileges in the system, disclose information or change the behavior of the system in some way beneficial to the attacker. If the application does not protect these critical tokens/parameters for integrity, it will not be able to determine that these values have been tampered with. Measures that are used to protect data for confidentiality should not be relied upon to provide the integrity service.
Potential Impact
Integrity
Unexpected State
Mitigations & Prevention
Protect important client controllable tokens/parameters for integrity using PKI methods (i.e. digital signatures) or other means, and checks for integrity on the server side.
Repeated requests from a particular user that include invalid values of tokens/parameters (those that should not be changed manually by users) should result in the user account lockout.
Client side tokens/parameters should not be such that it would be easy/predictable to guess another valid state.
Obfuscation should not be relied upon. If encryption is used, it needs to be properly applied (i.e. proven algorithm and implementation, use padding, use random initialization vector, user proper encryption mode). Even with proper encryption where the ciphertext does not leak information about the plaintext or reveal its structure, compromising integrity is possible (although less likely) without the provision of the integrity service.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2005-0039 | An IPSec configuration does not perform integrity checking of the IPSec packet as the result of either not configuring ESP properly to support the integrity service or using AH improperly. In either c |
Related Weaknesses
Frequently Asked Questions
What is CWE-649?
CWE-649 (Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.
How can CWE-649 be exploited?
Attackers can exploit CWE-649 (Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking) to unexpected state. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-649?
Key mitigations include: Protect important client controllable tokens/parameters for integrity using PKI methods (i.e. digital signatures) or other means, and checks for integrity on the server side.
What is the severity of CWE-649?
CWE-649 is classified as a Base-level weakness (Medium abstraction). It has been observed in 1 real-world CVEs.