CWE-602 服务端安全的客户端实施

Client-Side Enforcement of Server-Side Security

结构: Simple

Abstraction: Base

状态: Draft

被利用可能性: Medium

基本描述

The software is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.

扩展描述

When the server relies on protection mechanisms placed on the client side, an attacker can modify the client-side behavior to bypass the protection mechanisms resulting in potentially unexpected interactions between the client and server. The consequences will vary, depending on what the mechanisms are trying to protect.

相关缺陷

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

• cwe_Nature: ChildOf cwe_CWE_ID: 693 cwe_View_ID: 1000

• cwe_Nature: CanPrecede cwe_CWE_ID: 471 cwe_View_ID: 1000

• cwe_Nature: PeerOf cwe_CWE_ID: 290 cwe_View_ID: 1000

• cwe_Nature: PeerOf cwe_CWE_ID: 300 cwe_View_ID: 1000

适用平台

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

Paradigm: {'cwe_Name': 'Client Server', 'cwe_Prevalence': 'Sometimes'}

常见的影响

可能的缓解方案

Architecture and Design

策略:

For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.

Architecture and Design

策略:

If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source. Design the product so that this trust is managed in a centralized fashion, especially if there are complex or numerous communication channels, in order to reduce the risks that the implementer will mistakenly omit a check in a single code path.

Testing

策略:

Use dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

Testing

策略:

Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.

示例代码

例

This example contains client-side code that checks if the user authenticated successfully before sending a command. The server-side code performs the authentication in one step, and executes the command in a separate step.

CLIENT-SIDE (client.pl)

good Perl

SERVER-SIDE (server.pl):

bad

The server accepts 2 commands, "AUTH" which authenticates the user, and "CHANGE-ADDRESS" which updates the address field for the username. The client performs the authentication and only sends a CHANGE-ADDRESS for that user if the authentication succeeds. Because the client has already performed the authentication, the server assumes that the username in the CHANGE-ADDRESS is the same as the authenticated user. An attacker could modify the client by removing the code that sends the "AUTH" command and simply executing the CHANGE-ADDRESS.

分析过的案例

Notes

分类映射

相关攻击模式

• CAPEC-162
• CAPEC-202
• CAPEC-207
• CAPEC-208
• CAPEC-21
• CAPEC-31
• CAPEC-383
• CAPEC-384
• CAPEC-385
• CAPEC-386
• CAPEC-387
• CAPEC-388

引用

• REF-7 Writing Secure Code

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