CWE-837: 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.
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.
Consequences
- Other: Varies by Context
Recent advisories
- GHSA-pg53-p7qp-65cv — PocketMine-MP has potential memory/network vulnerability from repeated ResourcePackClientResponsePacket packets
- GHSA-rr73-568v-28f8 — Grav Vulnerable to Administrative Account Disruption and Privilege De-escalation via User Overwrite Logic
- GHSA-gc7q-jgjv-vjr2 — Keycloak Services has a potential bypass of brute force protection
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor