Bug 632240
Summary: | CVE-2010-3082 Django CSRF flaw [fedora-all] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Josh Bressers <bressers> |
Component: | Django | Assignee: | Steve Milner <smilner> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 13 | CC: | a.badger, dmalcolm, michel, mrunge, silas, smilner |
Target Milestone: | --- | Keywords: | Security, SecurityTracking |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Django-1.2.3-1.fc14 | Doc Type: | Release Note |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-23 12:57:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 632239 |
Description
Josh Bressers
2010-09-09 13:43:36 UTC
I'm working on the update now. More information: http://www.djangoproject.com/weblog/2010/sep/08/security-release/ Affects Django 1.2 series up to 1.2.2 Packages have been built and are requested for testing in Bodhi. I've changed the request to go to stable after running the F13 build with one of my own applications. Scratch that ... the update in bodhi was changed to go to testing (maybe it's automagic?). I guess we will wait until then. Ah. This security fix will be available late next week per https://fedoraproject.org/wiki/Package_update_acceptance_criteria as it was changed from stable to testing by bodhi. Filed a request with FESCo: https://fedorahosted.org/fesco/ticket/462 Additional update: http://www.djangoproject.com/weblog/2010/sep/10/123/ Today the Django team has released Django 1.2.3, which remedies several issues with the recent 1.2.2 package. This package corrects the following problems: * The patch applied for the security issue covered in Django 1.2.2 caused issues with non-ASCII responses using CSRF tokens. This has been remedied. * The patch also caused issues with some forms, most notably the user-editing forms in the Django administrative interface. This has been remedied. * The packaging manifest did not contain the full list of required files. This has been remedied. All users of Django are encouraged to upgrade to Django 1.2.3 immediately; the 1.2.3 package can be obtained from the Django downloads page, and as always signed checksums for the package are available. Thanks for the notice. I didn't seem to get this one in my email (as a packager). I'll upgrade it as soon as possible. Django-1.2.3-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/Django-1.2.3-1.fc13 Django-1.2.3-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/Django-1.2.3-1.fc14 Django-1.2.3-1.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/Django-1.2.3-1.fc12 Django-1.2.3-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update Django'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/Django-1.2.3-1.fc14 Django-1.2.3-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |