The linked vuln report gives the impression that regular parameter handling is vulnerable.
589 karma · joined May 1, 2010
The linked vuln report gives the impression that regular parameter handling is vulnerable.
However, that bug/exploit is based on the rails vuln and was patched in authlogic exactly how the Rails report instructed people to work around it (casting the parameter to a string).
Reading the actual report linked in the OP you'll see that generic and boilerplate code (e.g. the extremely common pattern: "Post.find_by_id(params[:id])") is going to be vulnerable to this bug.
From looking at it, it seems that ANY HTTP parameter (e.g. POST or GET - which are completely user-controlled) can be manipulated if you know how it's going to be used in the code, e.g. an obvious object ID.
EDIT: tenderlove sets it straight below
Lets not pretend that Ruby/Rails doesn't make major architectural decisions in favour of ease of use for the user.
e.g. if HTTP params weren't automatically marshalled into non-string data structures this bug wouldn't exist.
Thanks for the link.
My background processes lean on supervisor's functionality quite a lot. Most of them don't run any longer than 5 mins or so.
Always buy a nexus!
It will basically instruct it to continue to serve content that it considers "stale" (up to a point) until it is able to update it.
i.e. Python's standard library provides objects where appropriate, but often they will just put functions directly into modules for simplicity.
Different strokes, obviously, but just thought I'd mention an alternative.
"and that’s a particular worry for Oren Falkowitz, one of the developers of the database, who has left the NSA to start Sqrrl, a company that seeks to build a business around Accumulo in much the same way Red Hat built one around the Linux operating system."
Spaces, Tabs, OTBS, whatever. It doesn't matter which one was chosen, just that something was chosen. Ask the Pythonista's what PEP8 did for their developer's ecosystem.
Also it's important to note that that PSR-2 was based off already existing coding standards like Zend's and Symfony's.
More generally I would say it was interventionist, but very poorly handled. The issue is because they don't know what they're doing, rather than that they are subscribed to a certain style of government.
Say you want to add a product to an existing order in the database...
$orderProduct = new OrderProduct(); $order = OrderPeer::retrieveByPK(1);
$order->addOrderProduct($orderProduct);
Now, if ANYWHERE after this point in the code, something calls $order->getOrderProducts() before you call $order->save() (like a validation routine or something) you will lose that new OrderProduct and it will not be persisted.
It's bit me more than once, especially as you start to spread code around that depends on traversing the relationships - can be a very tricky bug to spot.
A lot about their active record implementation violates POLA with various gotchas and code generation gets tedious and unwieldy with models that contain many fields or relations.
I run half a dozen Django apps for less than $10/mo but they support any WSGI system, postgres or MySQL and their platform also handles your mail & DNS.
[0]. http://symfony.com/ [1]. http://silex.sensiolabs.org/ [2]. http://www.doctrine-project.org/
Both have to be done before pushing to remote, anyway.
I had some questions about whether using an md5sum as the bcrypt input, with much less keyspace (only hex characters) had any impact on security but nobody could/would answer.
I'm guessing that knowing that the plaintext for the bcrypt hash is always going to be 16 characters of 0-9,a-f might have some impact on crypto analysis but considering the passwords most people use I'm guessing it's only going to be a net win in terms of entropy.
Right, and what about the hundreds of other manufacturers of Android phones?