CWE-649: Reliance on Obfuscation or Encryption of Skip to content

Security weakness

CWE-649 Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking

A base-level weakness that can lead to data and pages or code changed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-649?

Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking: 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.

Business impact

What CWE-649 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Unexpected State

Free security check

Is CWE-649 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-649

Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking

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.

Weakness ID
CWE-649
Type
Base
Status
Incomplete
Likelihood of exploit
High
Introduced during
Architecture and Design, Implementation

Prevention

How to fix CWE-649, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • 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.
    Show 1 more recommendation
    • 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.

Detection and evidence

How CWE-649 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

Real vulnerabilities it caused

  • CVE-2005-0039An 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 case, the security.

How we fix it

From finding to fixed: how Codefreex closes CWE-649

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-649: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-649?

CWE-649, “Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. 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 serious is CWE-649?

MITRE rates the likelihood of exploit as High. It can affect integrity, with impacts such as unexpected state. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-649?

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.

Can Codefreex check my site for CWE-649?

Yes. A senior engineer reviews your site, store or app for CWE-649 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-649 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.