Tag Info

Rails 3 has some pretty good protections switched on by default which will catch a lot of common security issues. Specifically output encoding will help mitigate XSS attacks, the CSRF tokens are enabled by default on all forms which should help here, and as long as you use it correctly ActiveRecord or other ORMs can help with mitigating SQL injection. On ...

The OWASP XSS Cheat Sheet is a great resource to understand all the ways XSS can happen: RULE #0 - Never Insert Untrusted Data Except in Allowed Locations RULE #1 - HTML Escape Before Inserting Untrusted Data into HTML Element Content RULE #2 - Attribute Escape Before Inserting Untrusted Data into HTML Common Attributes RULE #3 - JavaScript Escape Before ...

Yes. You want Brakeman, a tool that scans your RoR code for security vulnerabilities I recommend reading the OWASP Ruby on Rails Security Guide. You could also try any web pen-testing tool; they are not language-specific. There are many of them. They only find low-hanging fruit, not all security problems, but it can't hurt to use them just in case they ...

You asked: Am I exposing potential vulnerabilities by exposing the same session cookie to all my users' subdomains? Answer: It depends, but generally speaking, yes, you could be exposing yourself to some attacks. It depends upon what kind of content you allow on the subdomains (e.g., elmer.acme.com). There are two cases: If you allow Elmer to put ...

It doesn't sound like you were hacked to me, it sounds more likely that Slicehost had some sort of issue temporarily. The SSH message you got means that the key that was sent by the server was different from the one in your cache. Here are possible reasons that come to mind: - Another server may have been temporarily assigned the IP address, and then the ...

Disclaimer: I'm one of the developers at Tinfoil Security. We have a free and quick check at https://www.tinfoilsecurity.com/railscheck. Tinfoil's check was based off of Metasploit's original probe. I'm curious as to why we came up as vulnerable when Metasploit did not -- feel free to email support@tinfoilsecurity.com or visit us at ...

Sorry for a short response, but I'm sure others will fill in eventually. RPORT most likely means the port that the webserver is running on. I've not used metasploit for this yet, unless Tinfoil Security uses the same concept, see: https://www.tinfoilsecurity.com/railscheck -k0nsl

I don't know how Slicehost works, but before considering the worst, I would try to contact them in order to have more information. As you are saying, you had a 20min down server, and when you tried to connect via SSH during this down time, your SSH key has changed. It can be an attack, but it's also possible that when a server is down, slicehost still ...

From the Ruby on Rails security Guide as long as you're using the reset_session command during the authentication process, you should be mitigating against session fixation attacks. In general with a rails app. if you're only creating the session when the user logs in and you're issuing a new Session ID at that point, you shouldn't have too many problems ...