Django security issues, new releases 1.10.7, 1.9.13, 1.8.18
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
Critical
|
MOS Maintenance | ||
8.0.x |
Fix Released
|
Critical
|
Max Yatsenko | ||
9.x |
Fix Released
|
Critical
|
Max Yatsenko |
Bug Description
Detailed bug description:
Today the Django team issued 1.10.7, 1.9.13, and 1.8.18 as part of our security process. These releases address two security issues, and we encourage all users to upgrade as soon as possible:
https:/
As a reminder, we ask that potential security issues be reported via private email to <email address hidden> and not via Django's Trac instance or the django-developers list. Please see https:/
How we are affected:
requirements.txt for Liberty:
https:/
Django>=1.7,<1.9
requirements.txt for Mitaka:
https:/
Django>=1.8,<1.9 # BSD
requirements.txt for Newton:
https:/
Django>=1.8,<1.9 # BSD
description: | updated |
Changed in mos: | |
importance: | High → Critical |
Changed in mos: | |
assignee: | nobody → MOS Linux (mos-linux) |
status: | New → Confirmed |
tags: | added: area-linux |
Changed in mos: | |
assignee: | MOS Linux (mos-linux) → MOS Maintenance (mos-maintenance) |
Changed in mos: | |
status: | Confirmed → Won't Fix |
Fix proposed to branch: master /review. fuel-infra. org/33081
Change author: Ivan Suzdal <email address hidden>
Review: https:/