Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Denial-of-service attack
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====Yo-yo attack==== A '''[[yo-yo]]''' attack is a specific type of DoS/DDoS aimed at [[cloud-hosted]] applications which use [[autoscaling]].<ref>{{cite journal |url=https://dl.acm.org/doi/10.1145/2829988.2790017 |title=Yo-Yo Attack: Vulnerability In Auto-scaling Mechanism |journal=ACM SIGCOMM Computer Communication Review |date=17 August 2015 |volume=45 |issue=4 |pages=103β104 |doi=10.1145/2829988.2790017 |last1=Sides |first1=Mor |last2=Bremler-Barr |first2=Anat |author-link2=Anat Bremler-Barr |last3=Rosensweig |first3=Elisha}}</ref><ref>{{cite book |title=Proceedings of the 11th International Conference on Cloud Computing and Services Science |chapter=Kubernetes Autoscaling: Yo ''Yo'' Attack Vulnerability and Mitigation |year=2021 |doi=10.5220/0010397900340044 |arxiv=2105.00542 |last1=Barr |first1=Anat |last2=Ben David |first2=Ronen |pages=34β44 |isbn=978-989-758-510-4 |s2cid=233482002}}</ref><ref>{{cite journal |title=Towards Yo-Yo attack mitigation in cloud auto-scaling mechanism |year=2020 |doi=10.1016/j.dcan.2019.07.002 |last1=Xu |first1=Xiaoqiong |last2=Li |first2=Jin |last3=Yu |first3=Hongfang |last4=Luo |first4=Long |last5=Wei |first5=Xuetao |last6=Sun |first6=Gang |journal=Digital Communications and Networks |volume=6 |issue=3 |pages=369β376 |s2cid=208093679 |doi-access=free}}</ref> The attacker generates a flood of traffic until a cloud-hosted service scales outwards to handle the increase of traffic, then halts the attack, leaving the victim with over-provisioned resources. When the victim scales back down, the attack resumes, causing resources to scale back up again. This can result in a reduced quality of service during the periods of scaling up and down and a financial drain on resources during periods of over-provisioning while operating with a lower cost for an attacker compared to a normal DDoS attack, as it only needs to be generating traffic for a portion of the attack period.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)