3467006 - Business Intelligence (BOE BI) No Rate Limit Vulnerability

• Vulnerability: Rate limiting is used to control the amount of incoming and outgoing traffic to or from a network.
• For example, let's say you are using a particular service's API that is configured to allow 100 requests/minute. If the number of requests you make exceeds that limit, then an error will be triggered.
• The reason behind implementing rate limits is to allow for a better flow of data and to increase security by mitigating attacks such as DDoS.
• Rate limiting also comes in useful if a particular user on the network makes a mistake in their request, thus asking the server to retrieve tons of information that may overload the network for everyone.
• With rate limiting in place, however, these types of errors or attacks are much more manageable.

• SAP BusinessObjects Business Intelligence Platform
• Tomcat

rate limit vulnerability, tomcat rate limit, request rate limit BI, rate limit BI Platform, application server rate limit , KBA , BI-BIP-SEC , Security Vulnerabilities in SAP BusinessObjects , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem