Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A business logic vulnerability lets someone gain unfairly by abusing a gap in a site's specification. Business logic means the rules of a site's business, such as how items are bought, the conditions of discounts, and the flow of bookings. OWASP describes it as a way of abusing the legitimate processing flow of an application.
How does a business logic vulnerability work?
Consider a shop with a points card. If the rule "once per purchase" can be used many times depending on the order of operations at the register, the rule has a hole. The machine is not broken, yet only the shop loses.
On a website too, if rules such as the conditions for combining discounts, or the order of a return and the granting of points, have gaps, someone can gain unfairly by extending ordinary screen operations. MITRE's CWE-840 treats such errors as a group of weaknesses in the business flow or sequence of actions, and explains that they look like legitimate use of a function, which makes them hard to find automatically.
OWASP says finding them requires an understanding of the business itself. To see what your own site shows from outside, you can start with the free URL check.
Why do business logic vulnerabilities matter?
Unlike a technical defect such as input handling, the cause is a hole in a rule that the designer did not notice. Online shops, booking sites, and member sites built to fit a particular business are more likely to be affected.
A review begins at the stage of deciding the specification, by asking how this rule could be abused. Alongside that, the upper limit on uses and the order of steps are checked on the server side, not on the screen.
In operation, records also help. OWASP's logging guide gives movements that try to skip steps, and movements that try to exceed the upper limit, as examples of what to record.
Related terms
- Insecure design: a problem where protection is missing at the design stage, before building starts
- Rate limiting: a limit that stops many accesses within a short time
- Race condition: a flaw that exploits a gap between simultaneous operations to make something process twice
- Vulnerability: a security hole
Frequently asked questions
Can an assessment tool find business logic vulnerabilities?
MITRE's CWE-840 explains that automated tools alone have a hard time finding them. OWASP points out that they cannot be seen without understanding the business itself. Someone who understands the flow of the business has to check, imagining how it could be abused.
Where should an online shop pay attention?
To flows where money or entitlement moves: coupons, points, returns, stock, and bookings. Ask your agency whether the upper limit on uses, the order of steps, and the conditions for combining offers are checked on the server side, not only on the screen.
Next step
The points to check are on the business logic vulnerability page. The free URL check covers only what is visible from outside, so contact us to review your own business rules.
Frequently asked questions
Can an assessment tool find business logic vulnerabilities?
MITRE's CWE-840 explains that automated tools alone have a hard time finding them. OWASP points out that they cannot be seen without understanding the business itself. Someone who understands the flow of the business has to check, imagining how it could be abused.
Where should an online shop pay attention?
To flows where money or entitlement moves: coupons, points, returns, stock, and bookings. Ask your agency whether the upper limit on uses, the order of steps, and the conditions for combining offers are checked on the server side, not only on the screen.