Difference between revisions of "WAF 340165"
(Created page with "'''Rule ID''' 340165 '''Status''' Active rule currently published. '''Alert Message''' Atomicorp.com WAF Rules: Remote File Injection attempt in URI (AE) '''Descripti...")
Latest revision as of 21:27, 4 March 2012
Active rule currently published.
Atomicorp.com WAF Rules: Remote File Injection attempt in URI (AE)
This rule detects Remote File Injection attempts. These types of attacks work by tricking an application into download software into itself, which will allow the attacker to download any software they want unto the victims systems, thereby compromising it.
This rules work by detecting the use of a URL as an argument in the URL, for example:
It will also try to determine if this is a local request, and if it is the local request will be allowed.
A false positive can occur when an application legitimately sets an argument to a URL, and does this using a previously unknown argument or method to store this URL. The rules contain a large library of known web applications and safe methods for using URLs, and can detect known safe methods and ignore them. However it is possible for a new or custom application to do this in an unknown manner and incorrectly trigger this rule.
It is not recommended that you disable this rule if you have a false positive. If you believe this is a false positive, please report this to our security team to determine if this is a legitimate case, or if its clever attack on your system. Instructions to report false positives are detailed on the Reporting False Positives wiki page. If it is a false positive, we will fix the issue in the rules and get a release out to you promptly.
If you know that this behavior is acceptable for your application, you can tune it by identifying the argument that is being triggered, and specifically allowing that argument for that application to allow a URL. Please see the Tuning the Atomicorp WAF Rules page for basic information.
Knowledge Base Articles