VERDICT —UNRATED
Verdict pending. Auto-ingested incidents are reviewed before a public verdict is rendered.
▰ METHOD
Undisclosed
Root cause
Root-cause analysis not yet published. The incident description below contains all currently available signal — review the attack transaction directly for definitive forensics.
Forensic narrative
The new version of DeversiFi encountered a vulnerability in less than a week after it was launched. The official said that it would be fixed as soon as possible. The cause of this vulnerability was that a trader tried to submit an order larger than the limit, and the logic of why the system designed order limit is to avoid user's misoperation. After that, the system still repeatedly submitted the order, but it was continuously rejected by the system, which affected the processing of other orders. Attack method (per SlowMist): System design defect. Reported loss: -.
Sourced from
slowmist
Technical record
- chain
- —
- protocol
- DeversiFi
- bug_class
- unknown
- date_occurred
- 2020-06-10
- loss_usd
- —
- source_id
- sm:deversifi::2020-06-10
Related — same bug class