5 ms·
FWIW, this is the third time in seven months that Rails had to issue a patch related to how ActiveRecord handles method parameters. 3.2.6 (June 2012) https://g
by danso 14y ago
FWIW, this is the third time in seven months that Rails had to issue a patch related to how ActiveRecord handles method parameters.
3.2.6 (June 2012)
https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/l4L0TEVAz1k https://groups.google.com/forum/?fromgroups=#!topic/rubyonra...
3.2.4 (May 2012)
https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/dUaiOOGWL1k https://groups.google.com/forum/?fromgroups=#!topic/rubyonra...
- dmix 14y agoI've always found Rails to be easy to secure compared to most other frameworks. I think the defaults are all pretty secure. I'd prefer having constant security patches. It shows people are still constantly testing it for vulnerabilities.
- biot 14y agoThat's a false dichotomy. I'd prefer to have people constantly test something for security vulnerabilities and find nothing because the code was thoroughly audited and shown to be secure before it was released.
- VMG 14y agoby that logic php is rock solid
- revelation 14y agoSQL injection is the web-equivalent of having a stack allocated buffer overflow. We have built and use (expensive) abstractions that supposedly eliminate these whole class of issues. With Rails, you get the expensive abstraction and apparently none of the security.
- phillmv 14y agoYes, clearly, because Rails has introduced absolutely no other kind of default protection. Is this an argument for hand rolling your own code, or for using some other framework that is apparently immune (or, to be charitable, has a stronger security track record)?
- srdev 14y agoLikely its an argument to use parameterized queries which fix the SQL injection problem altogether. I'm not familiar with Ruby, but surely they support it in 2013?
- qxcv 14y agoThey do, but what we're talking about here is an ORM, so there will always be machine generated SQL somewhere. Or do you believe that GP is suggesting that developers use parameterised SQL queries instead of an ORM?
- untog 14y agoEr, why can't the ORM use paramaterised queries?
- jeltz 14y agoThe problem is that ORMs like ActiveRecord really are just domain specific languages for building queries. If these DSLs use inband are carelessly constructed (e.g. they use some form of inband signaling) you can do the injection attack against the actual ORM code and make it build queries the author of the code did not intend.
- ssmoot 14y agoThat's a leap. Yehuda and I knew about the mass-assignment vulnerability during DataMapper v0.3, way back in the Merb days, before Rails3. Yet it didn't get addressed until a few months ago. PS: It's still broken IMO. It needed a rethinking of strategy and purpose. Instead it got a quick hack. If you want to see mass-assignment done right, look to Play Framework's First Class Forms support.
- steveklabnik 14y agoMass assignment as a feature is completely removed from Rails 4, and a gem with the replacement (strong_parameters) is available _today_ for you to use with any 3.x application.
- deleted 14y ago[deleted]
- charliesome 14y agoHistory seems to keep reminding us that in-band signalling is a convenient idea fraught with danger.
- josh2600 14y agoLook no further than the deprecated 5ESS switches which used to give up free calls due to 2600hz tones being signaled inband. Ask Steve Jobs and Woz about BlueBoxes; you need look no further to see the inherent dangers on inband signaling. Slightly off-topic, but still relevant IMHO.
- tptacek 14y agoBlue boxing predates 5ESS switches; 5ESS was notoriously the switch you couldn't blue-box.
- josh2600 14y agoOh really? I always thought SS7 was the first switch to move to out of band. What's the last blueBox-able switch?
- dalke 14y agoLet's see. Phrack Volume Three, Issue 25 says "In March of 1982, the 5ESS switch first went into operation." Esquire published "Secrets of the Little Blue Box" in the October 1971 issue of Esquire, based on the phone system MF design from the 1950s/1960s. That means blue boxing started at least 15 years before 5ESS, as tptacek pointed out. The 1987 Phreakers Manual (http://fringe.davesource.com/Fringe/Hacking/Phreaking/Phreakers_Manual http://fringe.davesource.com/Fringe/Hacking/Phreaking/Phreak... ) says "Blue boxing becomes harder as all Bell switching and transmission facilities go under to CCIS. Then to further complicate things, digital microwave, fiber optic, and satellite transmission are all coming to be digital and do not recognize 2600hz for the hang up signal. I predict that around 1990, blue boxes will be obsolete from all major cities." The 2600 FAQ, Section C-07, says (the earliest date I found for this was August 9, 1993): "Because of ESS Blue boxing is impossible". This is incorrect. ... While the advent of ESS (and other electronic switches) has made the blue boxers task a bit more difficult, ESS is not the reason most of you are unable to blue box. The main culprit is the "forward audio mute" feature of CCIS (out of band signalling). ... So for the clever amongst you, you must somehow get yourself to the 1000's of trunks out there that still utilize MF signalling but bypass/disable the CCIS audio mute problem. I don't know the switch models enough to say if it was exactly 5ESS, but everything suggests that that is the case.