Skip to content
OpenAdvisories

Weakness (CWE)

CWE-602: Client-Side Enforcement of Server-Side Security

Class Draft

The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.

How to prevent it (2 mitigations)

  1. 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.

  2. 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.

Source: MITRE CWE-602

All Critical High Medium Low Exploited only Public exploit

192 results · Feed