CWE-173: Improper Handling of Alternate Encoding

VariantDraft

The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-173: Improper Handling of Alternate Encoding?+

CWE-173: Improper Handling of Alternate Encoding is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.

What are the security consequences of Improper Handling of Alternate Encoding?+

If exploited, CWE-173 (Improper Handling of Alternate Encoding) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

Which programming languages are affected by Improper Handling of Alternate Encoding?+

CWE-173 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-173 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

CWE-173: Improper Handling of Alternate Encoding | CWE Lookup | InventiveHQ