日本語

CWE-573 詳細

CWE-573

Improper Following of Specification by Caller
2006-12-15
00h00 +00:00
Draft
2026-10-28
00h00 +00:00
CWE Mitre.org
特定のCWEの通知
特定のCWEの変更情報をいち早くお届けします。
通知を管理する

名前: Improper Following of Specification by Caller

The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.

一般情報

導入モード

Implementation

適用可能なプラットフォーム

言語

クラス： Not Language-Specific (Undetermined)

一般的な結果

スコープ 影響 可能性
OtherQuality Degradation, Varies by Context

注記：Unintended behaviors may result, possibly leaving the system vulnerable to any number of exploits.

観察された例

参考文献 説明

CVE-2006-7140

Crypto implementation removes padding when it shouldn't, allowing forged signatures

CVE-2006-4339

Crypto implementation removes padding when it shouldn't, allowing forged signatures

潜在的な緩和策

Phases : Implementation
When leveraging external functionality, such as an API, it is important that the caller does so in accordance with the requirements of the external functionality.

検出方法

Automated Static Analysis

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

脆弱性マッピングノート

理由 : This CWE entry is a Class and might have Base-level children that would be more appropriate
コメント : Examine children of this entry to see if there is a better fit

登録情報

名前 組織 日付 リリース日 Version
CWE Community 2006-12-15 +00:00 2006-12-15 +00:00 Draft 5

変更履歴

名前 組織 日付 コメント
Eric Dalci Cigital 2008-07-01 +00:00 updated Time_of_Introduction
CWE Content Team MITRE 2008-09-08 +00:00 updated Description, Relationships
CWE Content Team MITRE 2011-03-29 +00:00 updated Description, Name
CWE Content Team MITRE 2011-06-01 +00:00 updated Common_Consequences, Relationships, Taxonomy_Mappings
CWE Content Team MITRE 2011-06-27 +00:00 updated Common_Consequences
CWE Content Team MITRE 2012-05-11 +00:00 updated Relationships, Taxonomy_Mappings
CWE Content Team MITRE 2014-07-30 +00:00 updated Relationships
CWE Content Team MITRE 2017-01-19 +00:00 updated Relationships
CWE Content Team MITRE 2017-11-08 +00:00 updated Observed_Examples, Relationships
CWE Content Team MITRE 2019-01-03 +00:00 updated Relationships, Taxonomy_Mappings, Weakness_Ordinalities
CWE Content Team MITRE 2020-02-24 +00:00 updated Relationships
CWE Content Team MITRE 2023-01-31 +00:00 updated Description
CWE Content Team MITRE 2023-04-27 +00:00 updated Relationships
CWE Content Team MITRE 2023-06-29 +00:00 updated Mapping_Notes
CWE Content Team MITRE 2025-12-11 +00:00 updated Applicable_Platforms, Detection_Factors
CWE Content Team MITRE 2026-10-28 +00:00 updated Common_Consequences, Description, Potential_Mitigations, Relationships
CVE Findに掲載されている情報は、慎重に選定された複数の参照ソースから取得されています。CVEデータはMITRE Corporationおよび国家脆弱性データベース（NVD）が提供しています。既知の悪用された脆弱性（KEV）カタログはサイバーセキュリティ・インフラセキュリティ庁（CISA）から、EPSSスコアはFIRST.orgから取得しています。また、ソフトウェアの弱点（CWE）および共通攻撃パターン（CAPEC）に関するデータはMITRE Corporationが管理し、ハードウェアおよびソフトウェア構成（CPE）に関する情報はNVDが提供しています。