REDHAT-BUG-750658: High severity Django django-piston vulnerability
A flaw in Piston, a popular REST API framework for Django, was reported [1] in how it handles de-serialization of YAML post data. It uses the yaml.load method, which is unsafe and in certain circumstances could be used to allow remote execution of arbitrary code. The updated versions of Piston (0.2.3 and 0.2.2.1) correctly use the yaml.safeload method which prevents remote code execution.
This does not affect Django itself, but any users who have installed and use the django-piston package on Fedora may be vulnerable.
The upstream patch [2] is in git.
[1] https://www.djangoproject.com/weblog/2011/nov/01/piston-and-tastypie-security-releases/ [2] https://bitbucket.org/jespern/django-piston/changeset/91bdaec89543
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-750658?
The severity of REDHAT-BUG-750658 is critical due to the potential for remote code execution.
How do I fix REDHAT-BUG-750658?
To fix REDHAT-BUG-750658, upgrade to the latest version of django-piston that is no longer affected by the flaw.
What versions of django-piston are affected by REDHAT-BUG-750658?
Versions of django-piston from 0.2.2.1 to 0.2.3 are affected by REDHAT-BUG-750658.
What type of vulnerability is REDHAT-BUG-750658?
REDHAT-BUG-750658 is a deserialization vulnerability in how django-piston handles YAML data.
Can REDHAT-BUG-750658 be exploited remotely?
Yes, REDHAT-BUG-750658 can be exploited remotely to execute arbitrary code if the vulnerable version is in use.