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

Description

The product 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.

Common consequences

• Access Control,Availability→Bypass Protection Mechanism,DoS: Crash, Exit, or Restart
  Client-side validation checks can be easily bypassed, allowing malformed or unexpected input to pass into the application, potentially as trusted data. This may lead to unexpected states, behaviors and possibly a resulting crash.
• Access Control→Bypass Protection Mechanism,Gain Privileges or Assume Identity
  Client-side checks for authentication can be easily bypassed, allowing clients to escalate their access levels and perform unintended actions.

Potential mitigations

• Architecture and Design
  [object Object]
• 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

Related CWEs

Recent CVEs classified under this CWE