Detalle CWE-837

CWE-837

Improper Enforcement of a Single, Unique Action
2011-03-30
00h00 +00:00
Incomplete
2026-10-28
00h00 +00:00
Notificaciones para un CWE
Manténgase informado sobre cualquier cambio en un CWE específico.
Gestionar notificaciones

Nombre: Improper Enforcement of a Single, Unique Action

The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or incorrectly enforces this restriction.

Informaciones generales

Detalles de contexto

Modos de introducción

Implementation

Plataformas aplicables

Lenguaje

Clase: Not Language-Specific (Undetermined)

Tecnologías

Clase: Not Technology-Specific (Undetermined)
Clase: Web Based (Undetermined)
Nombre: Web Server (Undetermined)

Consecuencias comunes

Alcance Impacto Probabilidad
OtherVaries by Context

Note: An attacker might be able to gain advantage over other users by performing the action multiple times, or affect the correctness of the product.

Ejemplos observados

Referencias Descripción

CVE-2008-0294

Ticket-booking web application allows a user to lock a seat more than once.

CVE-2005-4051

CMS allows people to rate downloads by voting more than once.

CVE-2002-216

Polling software allows people to vote more than once by setting a cookie.

CVE-2003-1433

Chain: lack of validation of a challenge key in a game allows a player to register multiple times and lock other players out of the game.

CVE-2002-1018

Library feature allows attackers to check out the same e-book multiple times, preventing other users from accessing copies of the e-book.

CVE-2009-2346

Protocol implementation allows remote attackers to cause a denial of service (call-number exhaustion) by initiating many message exchanges.

Notas de mapeo de vulnerabilidades

Justificación : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comentario : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Envío

Nombre Organización Fecha Fecha de lanzamiento Version
CWE Content Team MITRE 2011-03-24 +00:00 2011-03-30 +00:00 1.12

Modificaciones

Nombre Organización Fecha Comentario
CWE Content Team MITRE 2012-05-11 +00:00 updated Observed_Examples
CWE Content Team MITRE 2020-02-24 +00:00 updated Relationships
CWE Content Team MITRE 2023-01-31 +00:00 updated Common_Consequences, 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 2023-10-26 +00:00 updated Common_Consequences
CWE Content Team MITRE 2025-12-11 +00:00 updated Applicable_Platforms, Time_of_Introduction, Weakness_Ordinalities
CWE Content Team MITRE 2026-10-28 +00:00 updated Background_Details, Demonstrative_Examples, Description