CWE-807Reliance on Untrusted Inputs in a Security Decision

Description

Common consequences· 1

• Confidentiality / Access Control / Availability / Other — Bypass Protection Mechanism, Gain Privileges or Assume Identity, Varies by Context
  Attackers can bypass the security decision to access whatever is being protected. The consequences will depend on the associated functionality, but they can range from granting additional privileges to untrusted users to bypassing important security checks. Ultimately, this weakness may lead to exposure or modification of sensitive data, system crash, or execution of arbitrary code.

Potential mitigations· 5

• [Architecture and Design]
• [Architecture and Design]
• [Architecture and Design]For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. 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.
• [Operation, Implementation]When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
• [Architecture and Design, Implementation]

(incoming)16

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.