CWE-837
Improper Enforcement of a Single, Unique Action
Incomplete
2011-03-30 00:00 +00:00
2023-10-26 00:00 +00:00
Alerte pour un CWE
Restez informé de toutes modifications pour un CWE spécifique.
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 improperly enforces this restriction.
Extended Description
In various applications, a user is only expected to perform a certain action once, such as voting, requesting a refund, or making a purchase. When this restriction is not enforced, sometimes this can have security implications. For example, in a voting application, an attacker could attempt to "stuff the ballot box" by voting multiple times. If these votes are counted separately, then the attacker could directly affect who wins the vote. This could have significant business impact depending on the purpose of the product.
Informations
Applicable Platforms
Language
Class: Not Language-Specific (Undetermined)Common Consequences
| Scope | Impact | Likelihood |
|---|---|---|
| Other | Varies 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. |
Observed Examples
| Reference | Description |
|---|---|
| Ticket-booking web application allows a user to lock a seat more than once. | |
| CMS allows people to rate downloads by voting more than once. | |
| Polling software allows people to vote more than once by setting a cookie. | |
| 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. | |
| Library feature allows attackers to check out the same e-book multiple times, preventing other users from accessing copies of the e-book. | |
| Protocol implementation allows remote attackers to cause a denial of service (call-number exhaustion) by initiating many message exchanges. |
Vulnerability Mapping Notes
Rationale : 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.Comments : 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.
Submission
| Name | Organization | Date | Date Release | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.12 |
Modifications
| Name | Organization | Date | Comment |
|---|---|---|---|
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences, Description | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Common_Consequences |
2024©
tesweb SA
