The built-in Rails logging system contains a significant amount of information about the running application - such as record of all requests, parameters sent, and queries performed. By default, the production log contains full requests and the value of every parameter, with no discretion.
An attacker who obtains the Rails production log could stumble upon [...]
A common cross site request forgery protection method is requiring a unique token to be submitted with each request. Rails uses a token that is submitted only with POST requests, and that token stays the same throughout the entire session, regardless of what form is being submitted. This is an effective way to mitigate most [...]
Null byte has posted a very simple web application “firewall” using only .htaccess mod_rewrite rules. It can effectively mitigate some basic web application attacks by filtering requests by patterns in the query string, such as XSS and command injection, as well as some of the more dangerous HTTP verbs. While it is definitely no [...]
Introduction to CSRF
Cross-site request forgery, or CSRF, is a common attack vector for web-based applications. In a nutshell, it allows the attacker to execute [destructive] actions in an application (through a HTTP request) on your behalf. It makes the assumption that you are already authenticated and have a valid session, and then makes the request [...]
It’s very common for open source web applications (as well as some commercial software) to place a “Powered by ____ version x.x.x” notice on publicly accessible pages. Other than advertising purposes, there is little or no reason to disclose this information. While some license agreements require that the notice stay visible, you can usually remove [...]
Posts
