let's say we have a WCF service, such as from the msdn examples - C #, calculatorservice, with all the default service settings.
If I were a hacker, and I knew that calculator service is something important, that I want to make it stop working, I can just hack the code for service links and create my own application that will create 10 clients. these clients will call a nonterminating method on the calculatorservice each time to keep the session alive and never close.
Now, obviously, since all 10 sessions are busy (or regardless of the number of maximum sessions), no one can access the calculator service, it is completely blocked!
How can we protect our services from this?
source
share