News for hackers. Stuff that matters.
Re:Ruby Security Have You Not by spatten on Thursday April 24, 2014 @02:30PM (#7642010)
The gems have probably been updated by the developers of the gem.

The data used in the article contains a list of the versions being used in production by real app, not the latest versions released by the gem developers.

Re:Ruby Security Have You Not by klochner on Thursday April 24, 2014 @02:41PM (#7642079)
Risk also depends on how you're using the gem.

If it's a bug in a YAML parser but you're not loading YAML from untrusted sources, then it would be a false positive.

Re:Ruby Security Have You Not by robotfelix on Thursday April 24, 2014 @03:40PM (#7642463)
Yes, after seeing many familiar gems in the graphic I was almost surprised to see that hakiri gave my Gemfile.lock an 'all clear'.

The should be able to calculate what percentage of these would still be vulnerable if fully updated - now that would be an interesting stat!

Re:Ruby Security Have You Not by vasinov on Thursday April 24, 2014 @02:34PM (#7642029)
I think unreal37 meant "once it's been reported, it would be fixed [in the app]." As in updated.
Re:Ruby Security Have You Not by unreal37 on Thursday April 24, 2014 @02:32PM (#7642017)
Ah, thanks for the clarification.