BUG BOUNTYFIELD MANUAL
Vulnerability reference
Markdown
0 / 5 checkedChecks last until this page reloads.

Sensitive business flow exceeds its permitted frequency or allocation

An actor exceeds an intended recipient, reservation, workflow or tenant allocation through repeated otherwise valid operations.

Candidate CWE: CWE-799

Test hypothesis#

Define the product rule and one synthetic recipient or allocation. In a local fixture with recording stubs, compare a permitted operation and the smallest sequence exceeding its configured limit; vary only one entry point, identity budget key, batch form or retry condition at a time.

Evidence required#

Record the intended allocation owner, all fixture identities, requests and committed effects, before/after counters and successful legitimate control. Explain the actual misuse rather than reporting missing automation friction. CWE-799 is a candidate when interaction frequency is the missing control.

Rule out false positives#

Automation, repeated valid actions, absent CAPTCHA or shared quotas may be intentional. Establish a prohibited business outcome; do not send real notifications, purchase scarce inventory or extrapolate unmeasured scale.

Playbook and command references#

Find the associated command snippets

Referenced by these target playbooks#

Report checklist#

  • Capture the affected version, configuration, identities, and object ownership.
  • Preserve a valid baseline and a negative control.
  • Reproduce the forbidden data access, action, or state change on controlled fixtures.
  • Explain the intended security rule and why the observed behavior violates it.
  • State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

Conditional ATT&CK mapping#

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.

Primary references#

Back to the complete vulnerability catalog