Re:What The Rails Security Issue Means For Your Startup
by piuk on Thursday January 31, 2013 @01:56PM
(#5146614)
Wouldn't the same origin policy prevent requests to localhost?
[ Parent
| on HN ]
Re:What The Rails Security Issue Means For Your Startup
by patio11 on Thursday January 31, 2013 @02:03PM
(#5146664)
You might be thinking of preventing Javascript on host X from sending XMLHttpRequests to host Y. That will not prevent Javascript on host X from adding a form to the web page and having it post to host Y with arbitrary content, or from having an IMG tag on host X attempt to load (via a GET) a URL on host Y (assuming someone finds a pathway that works via GET requests for these or related vulnerabilities).
Re:What The Rails Security Issue Means For Your Startup
by benmmurphy on Thursday January 31, 2013 @04:34PM
(#5147628)
afaik you can't use cross site requests to exploit either the xml bug or the json bug without also exploiting a browser or plugin bug. both issues depend on setting a request header and you are not allowed to do this in the browser security model. but it sucks that CSRF bug becomes RCE bug :(
Re:What The Rails Security Issue Means For Your Startup
by homakov on Thursday January 31, 2013 @04:40PM
(#5147662)
>but it sucks that CSRF bug becomes RCE bug :(
you just said it - it cant be exploited via CSRF. Because you cannot set header.
NO EXPLOIT FOR LOCALHOST:3000 calm down
Re:What The Rails Security Issue Means For Your Startup
by benmmurphy on Thursday January 31, 2013 @05:00PM
(#5147764)
i actually lied :) there is #from_xml so if you were doing Hash.from_xml(params[:trololol]) or Post.from_xml(params[:lols]) then you would be vulnerable to localhost:3000 attack. but I don't think there is generic attack it would have to be application specific.
Re:What The Rails Security Issue Means For Your Startup
by homakov on Friday February 01, 2013 @01:10AM
(#5149494)
you still needto bypass CSRF protection which is on by default
Re:What The Rails Security Issue Means For Your Startup
by rmc on Friday February 01, 2013 @01:58PM
(#5152609)
Yet.