CWE-841
Improper Enforcement of Behavioral Workflow
Incomplete
2011-03-30
00h00 +00:00
00h00 +00:00
2025-12-11
00h00 +00:00
00h00 +00:00
Benachrichtigungen für ein CWE
Bleiben Sie über alle Änderungen zu einem bestimmten CWE informiert.
Name: Improper Enforcement of Behavioral Workflow
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.
Allgemeine Informationen
Einführungsmodi
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.Anwendbare Plattformen
Sprache
Class: Not Language-Specific (Undetermined)Häufige Konsequenzen
| Bereich | Auswirkung | Wahrscheinlichkeit |
|---|---|---|
| Other | Alter Execution Logic Note: An attacker could cause the product to skip critical steps or perform them in the wrong order, bypassing its intended business logic. This can sometimes have security implications. |
Beobachtete Beispiele
| Referenzen | Beschreibung |
|---|---|
CVE-2011-0348 | Bypass of access/billing restrictions by sending traffic to an unrestricted destination before sending to a restricted destination. |
CVE-2007-3012 | Attacker can access portions of a restricted page by canceling out of a dialog. |
CVE-2009-5056 | Ticket-tracking system does not enforce a permission setting. |
CVE-2004-2164 | Shopping cart does not close a database connection when user restores a previous order, leading to connection exhaustion. |
CVE-2003-0777 | Chain: product does not properly handle dropped connections, leading to missing NULL terminator (CWE-170) and segmentation fault. |
CVE-2005-3327 | Chain: Authentication bypass by skipping the first startup step as required by the protocol. |
CVE-2004-0829 | Chain: File server crashes when sent a "find next" request without an initial "find first." |
CVE-2010-2620 | FTP server allows remote attackers to bypass authentication by sending (1) LIST, (2) RETR, (3) STOR, or other commands without performing the required login steps first. |
CVE-2005-3296 | FTP server allows remote attackers to list arbitrary directories as root by running the LIST command before logging in. |
Erkennungsmethoden
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)Hinweise zur Schwachstellen-Zuordnung
Begründung : 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.Kommentar : 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.
Hinweise
Referenzen
REF-795
Business Logic Flaws and Yahoo GamesJeremiah Grossman.
https://blog.jeremiahgrossman.com/2006/12/business-logic-flaws.html
REF-796
Seven Business Logic Flaws That Put Your Website At RiskJeremiah Grossman.
https://docplayer.net/10021793-Seven-business-logic-flaws-that-put-your-website-at-risk.html
REF-797
Business Logic FlawsWhiteHat Security.
https://web.archive.org/web/20080720171327/http://www.whitehatsec.com/home/solutions/BL_auction.html
REF-806
Insufficient Process ValidationWASC.
http://projects.webappsec.org/w/page/13246943/Insufficient-Process-Validation
REF-799
Defying Logic: Theory, Design, and Implementation of Complex Systems for Testing Application LogicRafal Los, Prajakta Jagdale.
https://www.slideshare.net/RafalLos/defying-logic-business-logic-testing-with-automation
REF-667
Real-Life Example of a 'Business Logic Defect' (Screen Shots!)Rafal Los.
http://h30501.www3.hp.com/t5/Following-the-White-Rabbit-A/Real-Life-Example-of-a-Business-Logic-Defect-Screen-Shots/ba-p/22581
REF-801
Toward Automated Detection of Logic Vulnerabilities in Web ApplicationsViktoria Felmetsger, Ludovico Cavedon, Christopher Kruegel, Giovanni Vigna.
https://www.usenix.org/legacy/events/sec10/tech/full_papers/Felmetsger.pdf
REF-802
Designing a Framework Method for Secure Business Application Logic Integrity in e-Commerce SystemsFaisal Nabi.
http://ijns.femto.com.tw/contents/ijns-v12-n1/ijns-2011-v12-n1-p29-41.pdf
Einreichung
| Name | Organisation | Datum | Veröffentlichungsdatum | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 1.12 |
Änderungen
| Name | Organisation | Datum | Kommentar |
|---|---|---|---|
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Common_Consequences, Observed_Examples, Related_Attack_Patterns, Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Observed_Examples, Relationships | |
| CWE Content Team | MITRE | updated Modes_of_Introduction, References, Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Common_Consequences, Description | |
| CWE Content Team | MITRE | updated References, Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Detection_Factors, Relationships, Type, Weakness_Ordinalities |
