CWE-177: Improper Handling of URL Encoding (Hex Encoding)

VariantDraft

The product does not properly handle when all or part of an input has been URL encoded.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-177: Improper Handling of URL Encoding (Hex Encoding)?+

CWE-177: Improper Handling of URL Encoding (Hex Encoding) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly handle when all or part of an input has been URL encoded.

What are the security consequences of Improper Handling of URL Encoding (Hex Encoding)?+

If exploited, CWE-177 (Improper Handling of URL Encoding (Hex Encoding)) it can compromise Integrity, leading to outcomes such as Unexpected State.

Which programming languages are affected by Improper Handling of URL Encoding (Hex Encoding)?+

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

What are real-world examples of Improper Handling of URL Encoding (Hex Encoding)?+

MITRE documents real CVEs mapped to CWE-177, including CVE-2000-0900, CVE-2005-2256, CVE-2004-2121, CVE-2004-0280 and CVE-2003-0424. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

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

A CWE (Common Weakness Enumeration) like CWE-177 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