Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-649 (依赖于未经完整性检查的安全相关输入的混淆或加密) — Vulnerability Class 5

5 vulnerabilities classified as CWE-649 (依赖于未经完整性检查的安全相关输入的混淆或加密). AI Chinese analysis included.

CWE-649 represents a critical integrity verification weakness where applications rely solely on obfuscation or encryption to secure security-relevant inputs without implementing robust integrity checks. This flaw allows attackers to exploit the system by intercepting and modifying encrypted or obfuscated data, such as tokens or parameters, which dictate user or system state. Since the application fails to validate whether the input has been altered during transit or storage, it blindly trusts the manipulated values, leading to unauthorized access, privilege escalation, or data corruption. Developers can prevent this vulnerability by implementing cryptographic signatures, hash-based message authentication codes (HMAC), or digital signatures alongside encryption. These mechanisms ensure that any tampering with the input is detected before processing, thereby maintaining data integrity and preventing attackers from exploiting the reliance on obscurity alone.

MITRE CWE 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.
Common Consequences (1)
IntegrityUnexpected State
The inputs could be modified without detection, causing the product to have unexpected system state or make incorrect security decisions.
Mitigations (4)
Architecture and DesignProtect 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.
Architecture and DesignRepeated 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.
Architecture and DesignClient side tokens/parameters should not be such that it would be easy/predictable to guess another valid state.
Architecture and DesignObfuscation 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 …

Vulnerabilities classified as CWE-649 (依赖于未经完整性检查的安全相关输入的混淆或加密) represent 5 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.