CWE-172 编码错误

admin 2022年1月7日03:00:25评论38 views字数 2680阅读8分56秒阅读模式

CWE-172 编码错误

Encoding Error

结构: Simple

Abstraction: Class

状态: Draft

被利用可能性: unkown

基本描述

The software does not properly encode or decode the data, resulting in unexpected values.

相关缺陷

  • cwe_Nature: ChildOf cwe_CWE_ID: 707 cwe_View_ID: 1000 cwe_Ordinal: Primary

  • cwe_Nature: CanPrecede cwe_CWE_ID: 22 cwe_View_ID: 1000

  • cwe_Nature: CanPrecede cwe_CWE_ID: 41 cwe_View_ID: 1000

适用平台

Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}

常见的影响

范围 影响 注释
Integrity Unexpected State

可能的缓解方案

MIT-5 Implementation

策略: Input Validation

Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). A blacklist is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

MIT-28 Implementation

策略: Output Encoding

While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict whitelist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection (CWE-88).

MIT-20 Implementation

策略: Input Validation

Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass whitelist validation schemes by introducing dangerous inputs after they have been checked.

Notes

Relationship
Partially overlaps path traversal and equivalence weaknesses.
Maintenance
This is more like a category than a weakness.
Maintenance
Many other types of encodings should be listed in this category.

分类映射

映射的分类名 ImNode ID Fit Mapped Node Name
PLOVER Encoding Error

相关攻击模式

  • CAPEC-120
  • CAPEC-267
  • CAPEC-3
  • CAPEC-52
  • CAPEC-53
  • CAPEC-64
  • CAPEC-71
  • CAPEC-72
  • CAPEC-78
  • CAPEC-80

文章来源于互联网:scap中文网

  • 左青龙
  • 微信扫一扫
  • weinxin
  • 右白虎
  • 微信扫一扫
  • weinxin
admin
  • 本文由 发表于 2022年1月7日03:00:25
  • 转载请保留本文链接(CN-SEC中文网:感谢原作者辛苦付出):
                   CWE-172 编码错误http://cn-sec.com/archives/612668.html

发表评论

匿名网友 填写信息