| 1 |
========================== |
| 2 |
Archive of security issues |
| 3 |
========================== |
| 4 |
|
| 5 |
Django's development team is strongly committed to responsible |
| 6 |
reporting and disclosure of security-related issues, as outlined in |
| 7 |
:doc:`Django's security policies </internals/security>`. |
| 8 |
|
| 9 |
As part of that commitment, we maintain the following historical list |
| 10 |
of issues which have been fixed and disclosed. For each issue, the |
| 11 |
list below includes the date, a brief description, the `CVE identifier |
| 12 |
<https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures>`_ |
| 13 |
if applicable, a list of affected versions, a link to the full |
| 14 |
disclosure and links to the appropriate patch(es). |
| 15 |
|
| 16 |
Some important caveats apply to this information: |
| 17 |
|
| 18 |
* Lists of affected versions include only those versions of Django |
| 19 |
which had stable, security-supported releases at the time of |
| 20 |
disclosure. This means older versions (whose security support had |
| 21 |
expired) and versions which were in pre-release (alpha/beta/RC) |
| 22 |
states at the time of disclosure may have been affected, but are not |
| 23 |
listed. |
| 24 |
|
| 25 |
* The Django project has on occasion issued security advisories, |
| 26 |
pointing out potential security problems which can arise from |
| 27 |
improper configuration or from other issues outside of Django |
| 28 |
itself. Some of these advisories have received CVEs; when that is |
| 29 |
the case, they are listed here, but as they have no accompanying |
| 30 |
patches or releases, only the description, disclosure and CVE will |
| 31 |
be listed. |
| 32 |
|
| 33 |
Issues under Django's security process |
| 34 |
====================================== |
| 35 |
|
| 36 |
All security issues have been handled under versions of Django's security |
| 37 |
process. These are listed below. |
| 38 |
|
| 39 |
May 5, 2026 - :cve:`2026-5766` |
| 40 |
------------------------------ |
| 41 |
|
| 42 |
Potential denial-of-service vulnerability in ASGI requests via file upload |
| 43 |
limit bypass. |
| 44 |
`Full description |
| 45 |
<https://www.djangoproject.com/weblog/2026/may/05/security-releases/>`__ |
| 46 |
|
| 47 |
* Django 6.0 :commit:`(patch) <ad8f9e19e0897ea45ded7c046ff28daf6f773e92>` |
| 48 |
* Django 5.2 :commit:`(patch) <2ec27eda3ba6c14f0856e6e3eb1df07c41fd95e6>` |
| 49 |
|
| 50 |
May 5, 2026 - :cve:`2026-35192` |
| 51 |
------------------------------- |
| 52 |
|
| 53 |
Session fixation via public cached pages and ``SESSION_SAVE_EVERY_REQUEST``. |
| 54 |
`Full description |
| 55 |
<https://www.djangoproject.com/weblog/2026/may/05/security-releases/>`__ |
| 56 |
|
| 57 |
* Django 6.0 :commit:`(patch) <1b0184aa657bc3f5859aeb0206e7c1e94e48b103>` |
| 58 |
* Django 5.2 :commit:`(patch) <47cf968c125e3fab317e10fe150ec479e745f995>` |
| 59 |
|
| 60 |
May 5, 2026 - :cve:`2026-6907` |
| 61 |
------------------------------ |
| 62 |
|
| 63 |
Potential exposure of private data due to incorrect handling of ``Vary: *`` in |
| 64 |
``UpdateCacheMiddleware``. |
| 65 |
`Full description |
| 66 |
<https://www.djangoproject.com/weblog/2026/may/05/security-releases/>`__ |
| 67 |
|
| 68 |
* Django 6.0 :commit:`(patch) <44ad76efcbe3c4ca0f08bb9dabe916f6374596c9>` |
| 69 |
* Django 5.2 :commit:`(patch) <2115d4eaee15107f5cd290d7cfcc5ffe3ad43661>` |
| 70 |
|
| 71 |
April 7, 2026 - :cve:`2026-3902` |
| 72 |
-------------------------------- |
| 73 |
|
| 74 |
ASGI header spoofing via underscore/hyphen conflation. |
| 75 |
`Full description |
| 76 |
<https://www.djangoproject.com/weblog/2026/apr/07/security-releases/>`__ |
| 77 |
|
| 78 |
* Django 6.0 :commit:`(patch) <a623c3982857e80324448f85c7faf9a6710330ef>` |
| 79 |
* Django 5.2 :commit:`(patch) <1cc2a7612f97c109b92415fc11ba9bd0501852e0>` |
| 80 |
* Django 4.2 :commit:`(patch) <4412731aa64d62a6dd7edae79e0c15b72666d7ca>` |
| 81 |
|
| 82 |
April 7, 2026 - :cve:`2026-4277` |
| 83 |
-------------------------------- |
| 84 |
|
| 85 |
Privilege abuse in ``GenericInlineModelAdmin``. |
| 86 |
`Full description |
| 87 |
<https://www.djangoproject.com/weblog/2026/apr/07/security-releases/>`__ |
| 88 |
|
| 89 |
* Django 6.0 :commit:`(patch) <08a752c1cd8f378b4c64d96c319da23726df6ed3>` |
| 90 |
* Django 5.2 :commit:`(patch) <60ffa957c427e10a2eb0fc80d1674a8a8ccc30b0>` |
| 91 |
* Django 4.2 :commit:`(patch) <051f3909e820360bbe84a21350e82f4961e3d917>` |
| 92 |
|
| 93 |
April 7, 2026 - :cve:`2026-4292` |
| 94 |
-------------------------------- |
| 95 |
|
| 96 |
Privilege abuse in ``ModelAdmin.list_editable``. |
| 97 |
`Full description |
| 98 |
<https://www.djangoproject.com/weblog/2026/apr/07/security-releases/>`__ |
| 99 |
|
| 100 |
* Django 6.0 :commit:`(patch) <428c48f358c5a0ed5ca2834fb721d615eb2b0e11>` |
| 101 |
* Django 5.2 :commit:`(patch) <397c22048244db2cd4bb78f570e6c72a3967bf36>` |
| 102 |
* Django 4.2 :commit:`(patch) <abfe1a1c57a57cfaf6dd4a0571c029401a0fe743>` |
| 103 |
|
| 104 |
April 7, 2026 - :cve:`2026-33033` |
| 105 |
--------------------------------- |
| 106 |
|
| 107 |
Potential denial-of-service vulnerability in ``MultiPartParser`` via |
| 108 |
base64-encoded file upload. |
| 109 |
`Full description |
| 110 |
<https://www.djangoproject.com/weblog/2026/apr/07/security-releases/>`__ |
| 111 |
|
| 112 |
* Django 6.0 :commit:`(patch) <0910af60468216c856dfbcac1177372c225deb76>` |
| 113 |
* Django 5.2 :commit:`(patch) <0b467893bdde69a2d23034338e76021a1e4f4322>` |
| 114 |
* Django 4.2 :commit:`(patch) <f13c20f81b56108ac477213fa5ada2524b5e5c98>` |
| 115 |
|
| 116 |
April 7, 2026 - :cve:`2026-33034` |
| 117 |
--------------------------------- |
| 118 |
|
| 119 |
Potential denial-of-service vulnerability in ASGI requests via memory upload |
| 120 |
limit bypass. |
| 121 |
`Full description |
| 122 |
<https://www.djangoproject.com/weblog/2026/apr/07/security-releases/>`__ |
| 123 |
|
| 124 |
* Django 6.0 :commit:`(patch) <393dbc53e848876fdba92fbf02e10ee6a6eace6b>` |
| 125 |
* Django 5.2 :commit:`(patch) <49e1e2b548999a35a025f9682598946bda9e9921>` |
| 126 |
* Django 4.2 :commit:`(patch) <ed4dfda62718a0bb644b80ac8b1d3099861f2295>` |
| 127 |
|
| 128 |
March 3, 2026 - :cve:`2026-25673` |
| 129 |
--------------------------------- |
| 130 |
|
| 131 |
Potential denial-of-service vulnerability in ``URLField`` via Unicode |
| 132 |
normalization on Windows. |
| 133 |
`Full description |
| 134 |
<https://www.djangoproject.com/weblog/2026/mar/03/security-releases/>`__ |
| 135 |
|
| 136 |
* Django 6.0 :commit:`(patch) <b1444d9acf43db9de96e0da2b4737ad56af0eb76>` |
| 137 |
* Django 5.2 :commit:`(patch) <4d3c184686626d224d9a87451410ecf802b41f7c>` |
| 138 |
* Django 4.2 :commit:`(patch) <b3e8ec8cc310489fe80174b14b11edb970d682ea>` |
| 139 |
|
| 140 |
March 3, 2026 - :cve:`2026-25674` |
| 141 |
--------------------------------- |
| 142 |
|
| 143 |
Potential incorrect permissions on newly created file system objects. |
| 144 |
`Full description |
| 145 |
<https://www.djangoproject.com/weblog/2026/mar/03/security-releases/>`__ |
| 146 |
|
| 147 |
* Django 6.0 :commit:`(patch) <264d5c70ef3281a8869cb2ad45a3a52d5adbe790>` |
| 148 |
* Django 5.2 :commit:`(patch) <b07ed2a1e445efde54fc64cb8c37e0f4f7fe53e5>` |
| 149 |
* Django 4.2 :commit:`(patch) <54b50bf7d6dcbf02d4c01f853627cc9299d4934d>` |
| 150 |
|
| 151 |
February 3, 2026 - :cve:`2025-13473` |
| 152 |
------------------------------------ |
| 153 |
|
| 154 |
Username enumeration through timing difference in mod_wsgi authentication |
| 155 |
handler. |
| 156 |
`Full description |
| 157 |
<https://www.djangoproject.com/weblog/2026/feb/03/security-releases/>`__ |
| 158 |
|
| 159 |
* Django 6.0 :commit:`(patch) <d72cc3be3be0bbebdcaea5a8c8106b4d6f2a32bd>` |
| 160 |
* Django 5.2 :commit:`(patch) <184e38ab0a061c365f5775676a074796d8abd02f>` |
| 161 |
* Django 4.2 :commit:`(patch) <6dc23508f3395e1254c315084c7334ef81c4c09a>` |
| 162 |
|
| 163 |
February 3, 2026 - :cve:`2025-14550` |
| 164 |
------------------------------------ |
| 165 |
|
| 166 |
Potential denial-of-service vulnerability via repeated headers when using ASGI. |
| 167 |
`Full description |
| 168 |
<https://www.djangoproject.com/weblog/2026/feb/03/security-releases/>`__ |
| 169 |
|
| 170 |
* Django 6.0 :commit:`(patch) <972dbdd4f7f69e9c405e6fe12a1b90e4713c1611>` |
| 171 |
* Django 5.2 :commit:`(patch) <1ba90069c12836db46981bdf75b0e661db5849ce>` |
| 172 |
* Django 4.2 :commit:`(patch) <f578acc8c54530fffabd52d2db654c8669b011af>` |
| 173 |
|
| 174 |
February 3, 2026 - :cve:`2026-1207` |
| 175 |
----------------------------------- |
| 176 |
|
| 177 |
Potential SQL injection via raster lookups on PostGIS. |
| 178 |
`Full description |
| 179 |
<https://www.djangoproject.com/weblog/2026/feb/03/security-releases/>`__ |
| 180 |
|
| 181 |
* Django 6.0 :commit:`(patch) <8f77e7301174834573614ae90e1826fdf27f8a24>` |
| 182 |
* Django 5.2 :commit:`(patch) <17a1d64a58ef24c0c3b78d66d86f5415075f18f0>` |
| 183 |
* Django 4.2 :commit:`(patch) <a14363102d98fa29b8cced578eb3a0fadaa5bcb7>` |
| 184 |
|
| 185 |
February 3, 2026 - :cve:`2026-1285` |
| 186 |
----------------------------------- |
| 187 |
|
| 188 |
Potential denial-of-service vulnerability in ``django.utils.text.Truncator`` |
| 189 |
HTML methods. |
| 190 |
`Full description |
| 191 |
<https://www.djangoproject.com/weblog/2026/feb/03/security-releases/>`__ |
| 192 |
|
| 193 |
* Django 6.0 :commit:`(patch) <4b86ba51e486530db982341a23e53c7a1e1e6e71>` |
| 194 |
* Django 5.2 :commit:`(patch) <9f2ada875bbee62ac46032e38ddb22755d67ae5a>` |
| 195 |
* Django 4.2 :commit:`(patch) <b40cfc6052ced26dcd8166a58ea6f841d0d2cac8>` |
| 196 |
|
| 197 |
February 3, 2026 - :cve:`2026-1287` |
| 198 |
----------------------------------- |
| 199 |
|
| 200 |
Potential SQL injection in column aliases via control characters. |
| 201 |
`Full description |
| 202 |
<https://www.djangoproject.com/weblog/2026/feb/03/security-releases/>`__ |
| 203 |
|
| 204 |
* Django 6.0 :commit:`(patch) <0c0f5c2178c01ada5410cd53b4b207bf7858b952>` |
| 205 |
* Django 5.2 :commit:`(patch) <3e68ccdc11c127758745ddf0b4954990b14892bc>` |
| 206 |
* Django 4.2 :commit:`(patch) <f75f8f3597e1ce351d5ac08b6ba7ebd9dadd9b5d>` |
| 207 |
|
| 208 |
February 3, 2026 - :cve:`2026-1312` |
| 209 |
----------------------------------- |
| 210 |
|
| 211 |
Potential SQL injection via ``QuerySet.order_by`` and ``FilteredRelation``. |
| 212 |
`Full description |
| 213 |
<https://www.djangoproject.com/weblog/2026/feb/03/security-releases/>`__ |
| 214 |
|
| 215 |
* Django 6.0 :commit:`(patch) <15e70cb83e6f7a9a2a2f651f30b28b5cb20febeb>` |
| 216 |
* Django 5.2 :commit:`(patch) <e863ee273c6553e9b6fa4960a17acb535851857b>` |
| 217 |
* Django 4.2 :commit:`(patch) <90f5b10784ba5bf369caed87640e2b4394ea3314>` |
| 218 |
|
| 219 |
December 2, 2025 - :cve:`2025-13372` |
| 220 |
------------------------------------ |
| 221 |
|
| 222 |
Potential SQL injection in ``FilteredRelation`` column aliases on PostgreSQL. |
| 223 |
`Full description |
| 224 |
<https://www.djangoproject.com/weblog/2025/dec/02/security-releases/>`__ |
| 225 |
|
| 226 |
* Django 6.0 :commit:`(patch) <56aea00c3c5e1aacf4ed05f8ee06c2e78f02cea0>` |
| 227 |
* Django 5.2 :commit:`(patch) <479415ce5249bcdebeb6570c72df2a87f45a7bbf>` |
| 228 |
* Django 5.1 :commit:`(patch) <9c6a5bde24240382807d13bc3748d08444709355>` |
| 229 |
* Django 4.2 :commit:`(patch) <f997037b235f6b5c9e7c4a501491ec45f3400f3d>` |
| 230 |
|
| 231 |
December 2, 2025 - :cve:`2025-64460` |
| 232 |
------------------------------------ |
| 233 |
|
| 234 |
Potential denial-of-service vulnerability in XML serializer text extraction. |
| 235 |
`Full description |
| 236 |
<https://www.djangoproject.com/weblog/2025/dec/02/security-releases/>`__ |
| 237 |
|
| 238 |
* Django 6.0 :commit:`(patch) <1dbd07a608e495a0c229edaaf84d58d8976313b5>` |
| 239 |
* Django 5.2 :commit:`(patch) <99e7d22f55497278d0bcb2e15e72ef532e62a31d>` |
| 240 |
* Django 5.1 :commit:`(patch) <0db9ea4669312f1f4973e09f4bca06ab9c1ec74b>` |
| 241 |
* Django 4.2 :commit:`(patch) <4d2b8803bebcdefd2b76e9e8fc528d5fddea93f0>` |
| 242 |
|
| 243 |
November 5, 2025 - :cve:`2025-64458` |
| 244 |
------------------------------------ |
| 245 |
|
| 246 |
Potential denial-of-service vulnerability in ``HttpResponseRedirect`` and |
| 247 |
``HttpResponsePermanentRedirect`` on Windows. `Full description |
| 248 |
<https://www.djangoproject.com/weblog/2025/nov/05/security-releases/>`__ |
| 249 |
|
| 250 |
* Django 6.0 :commit:`(patch) <6e13348436fccf8f22982921d6a3a3e65c956a9f>` |
| 251 |
* Django 5.2 :commit:`(patch) <4f5d904b63751dea9ffc3b0e046404a7fa5881ac>` |
| 252 |
* Django 5.1 :commit:`(patch) <3790593781d26168e7306b5b2f8ea0309de16242>` |
| 253 |
* Django 4.2 :commit:`(patch) <770eea38d7a0e9ba9455140b5a9a9e33618226a7>` |
| 254 |
|
| 255 |
November 5, 2025 - :cve:`2025-64459` |
| 256 |
------------------------------------ |
| 257 |
|
| 258 |
Potential SQL injection via ``_connector`` keyword argument in ``QuerySet`` and |
| 259 |
``Q`` objects. `Full description |
| 260 |
<https://www.djangoproject.com/weblog/2025/nov/05/security-releases/>`__ |
| 261 |
|
| 262 |
* Django 6.0 :commit:`(patch) <06dd38324ac3d60d83d9f3adabf0dcdf423d2a85>` |
| 263 |
* Django 5.2 :commit:`(patch) <6703f364d767e949c5b0e4016433ef75063b4f9b>` |
| 264 |
* Django 5.1 :commit:`(patch) <72d2c87431f2ae0431d65d0ec792047f078c8241>` |
| 265 |
* Django 4.2 :commit:`(patch) <59ae82e67053d281ff4562a24bbba21299f0a7d4>` |
| 266 |
|
| 267 |
October 1, 2025 - :cve:`2025-59681` |
| 268 |
----------------------------------- |
| 269 |
|
| 270 |
Potential SQL injection in ``QuerySet.annotate()``, ``alias()``, |
| 271 |
``aggregate()``, and ``extra()`` on MySQL and MariaDB. `Full description |
| 272 |
<https://www.djangoproject.com/weblog/2025/oct/01/security-releases/>`__ |
| 273 |
|
| 274 |
* Django 6.0 :commit:`(patch) <4ceaaee7e04b416fc465e838a6ef43ca0ccffafe>` |
| 275 |
* Django 5.2 :commit:`(patch) <52fbae0a4dbbe5faa59827f8f05694a0065cc135>` |
| 276 |
* Django 5.1 :commit:`(patch) <01d2d770e22bffe53c7f1e611e2bbca94cb8a2e7>` |
| 277 |
* Django 4.2 :commit:`(patch) <38d9ef8c7b5cb6ef51b933e51a20e0e0063f33d5>` |
| 278 |
|
| 279 |
October 1, 2025 - :cve:`2025-59682` |
| 280 |
----------------------------------- |
| 281 |
|
| 282 |
Potential partial directory-traversal via ``archive.extract()``. |
| 283 |
`Full description |
| 284 |
<https://www.djangoproject.com/weblog/2025/oct/01/security-releases/>`__ |
| 285 |
|
| 286 |
* Django 6.0 :commit:`(patch) <af067f56c1dd467df4abd0ddd409a700da1f03ba>` |
| 287 |
* Django 5.2 :commit:`(patch) <ed8fc39d77465eddbde1191a054ae965f6a8a584>` |
| 288 |
* Django 5.1 :commit:`(patch) <74fa85c688a87224637155902bcd738bb9e65e11>` |
| 289 |
* Django 4.2 :commit:`(patch) <9504bbaa392c9fe37eee9291f5b4c29eb6037619>` |
| 290 |
|
| 291 |
September 3, 2025 - :cve:`2025-57833` |
| 292 |
------------------------------------- |
| 293 |
|
| 294 |
Potential SQL injection in ``FilteredRelation`` column aliases. |
| 295 |
`Full description |
| 296 |
<https://www.djangoproject.com/weblog/2025/sep/03/security-releases/>`__ |
| 297 |
|
| 298 |
* Django 5.2 :commit:`(patch) <4c044fcc866ec226f612c475950b690b0139d243>` |
| 299 |
* Django 5.1 :commit:`(patch) <102965ea93072fe3c39a30be437c683ec1106ef5>` |
| 300 |
* Django 4.2 :commit:`(patch) <31334e6965ad136a5e369993b01721499c5d1a92>` |
| 301 |
|
| 302 |
June 4, 2025 - :cve:`2025-48432` |
| 303 |
-------------------------------- |
| 304 |
|
| 305 |
Potential log injection via unescaped request path. |
| 306 |
`Full description |
| 307 |
<https://www.djangoproject.com/weblog/2025/jun/04/security-releases/>`__ |
| 308 |
|
| 309 |
* Django 5.2 :commit:`(patch) <7456aa23dafa149e65e62f95a6550cdb241d55ad>` |
| 310 |
* Django 5.1 :commit:`(patch) <596542ddb46cdabe011322917e1655f0d24eece2>` |
| 311 |
* Django 4.2 :commit:`(patch) <ac03c5e7df8680c61cdb0d3bdb8be9095dba841e>` |
| 312 |
|
| 313 |
There was an additional hardening with new patch releases published on June 10, |
| 314 |
2025. `Full description |
| 315 |
<https://www.djangoproject.com/weblog/2025/jun/10/bugfix-releases/>`__ |
| 316 |
|
| 317 |
* Django 5.2.3 :commit:`(patch) <8fcc83953c350e158a484bf1da0aa1b79b69bb07>` |
| 318 |
* Django 5.1.11 :commit:`(patch) <31f4bd31fa16f7f5302f65b9b8b7a49b69a7c4a6>` |
| 319 |
* Django 4.2.23 :commit:`(patch) <b597d46bb19c8567615e62029210dab16c70db7d>` |
| 320 |
|
| 321 |
May 7, 2025 - :cve:`2025-32873` |
| 322 |
------------------------------- |
| 323 |
|
| 324 |
Denial-of-service possibility in ``strip_tags()``. |
| 325 |
`Full description |
| 326 |
<https://www.djangoproject.com/weblog/2025/may/07/security-releases/>`__ |
| 327 |
|
| 328 |
* Django 5.2 :commit:`(patch) <c9731dc656e533187b021b4d81f8293d6c943a43>` |
| 329 |
* Django 5.1 :commit:`(patch) <0b42f6a528df966729b24ecaaed67f85e5edc3dc>` |
| 330 |
* Django 4.2 :commit:`(patch) <9cd8028f3e38dca8e51c1388f474eecbe7d6ca3c>` |
| 331 |
|
| 332 |
April 2, 2025 - :cve:`2025-27556` |
| 333 |
--------------------------------- |
| 334 |
|
| 335 |
Potential denial-of-service vulnerability in ``LoginView``, ``LogoutView``, and |
| 336 |
``set_language()`` on Windows. `Full description |
| 337 |
<https://www.djangoproject.com/weblog/2025/apr/02/security-releases/>`__ |
| 338 |
|
| 339 |
* Django 5.1 :commit:`(patch) <edc2716d01a6fdd84b173c02031695231bcee1f8>` |
| 340 |
* Django 5.0 :commit:`(patch) <8c6871b097b6c49d2a782c0d80d908bcbe2116f1>` |
| 341 |
|
| 342 |
March 6, 2025 - :cve:`2025-26699` |
| 343 |
--------------------------------- |
| 344 |
|
| 345 |
Potential denial-of-service in ``django.utils.text.wrap()``. |
| 346 |
`Full description |
| 347 |
<https://www.djangoproject.com/weblog/2025/mar/06/security-releases/>`__ |
| 348 |
|
| 349 |
* Django 5.1 :commit:`(patch) <8dbb44d34271637099258391dfc79df33951b841>` |
| 350 |
* Django 5.0 :commit:`(patch) <4f2765232336b8ad0afd8017d9d912ae93470017>` |
| 351 |
* Django 4.2 :commit:`(patch) <e88f7376fe68dbf4ebaf11fad1513ce700b45860>` |
| 352 |
|
| 353 |
January 14, 2025 - :cve:`2024-56374` |
| 354 |
------------------------------------ |
| 355 |
|
| 356 |
Potential denial-of-service vulnerability in IPv6 validation. |
| 357 |
`Full description |
| 358 |
<https://www.djangoproject.com/weblog/2025/jan/14/security-releases/>`__ |
| 359 |
|
| 360 |
* Django 5.1 :commit:`(patch) <4806731e58f3e8700a3c802e77899d54ac6021fe>` |
| 361 |
* Django 5.0 :commit:`(patch) <e8d4a2005955dcf962193600b53bf461b190b455>` |
| 362 |
* Django 4.2 :commit:`(patch) <ad866a1ca3e7d60da888d25d27e46a8adb2ed36e>` |
| 363 |
|
| 364 |
December 4, 2024 - :cve:`2024-53907` |
| 365 |
------------------------------------ |
| 366 |
|
| 367 |
Potential denial-of-service in ``django.utils.html.strip_tags()``. |
| 368 |
`Full description |
| 369 |
<https://www.djangoproject.com/weblog/2024/dec/04/security-releases/>`__ |
| 370 |
|
| 371 |
* Django 5.1 :commit:`(patch) <bbc74a7f7eb7335e913bdb4787f22e83a9be947e>` |
| 372 |
* Django 5.0 :commit:`(patch) <a5a89ea28cc550c1b29b03f9e14ef3c128ec1e84>` |
| 373 |
* Django 4.2 :commit:`(patch) <790eb058b0716c536a2f2e8d1c6d5079d776c22b>` |
| 374 |
|
| 375 |
December 4, 2024 - :cve:`2024-53908` |
| 376 |
------------------------------------ |
| 377 |
|
| 378 |
Potential SQL injection in ``HasKey(lhs, rhs)`` on Oracle. |
| 379 |
`Full description |
| 380 |
<https://www.djangoproject.com/weblog/2024/dec/04/security-releases/>`__ |
| 381 |
|
| 382 |
* Django 5.1 :commit:`(patch) <6943d61818e63e77b65d8b1ae65941e8f04bd87b>` |
| 383 |
* Django 5.0 :commit:`(patch) <ff08bb6c70aa45f83a5ef3bd0b601c7c9d1a7642>` |
| 384 |
* Django 4.2 :commit:`(patch) <7376bcbf508883282ffcc0f0fac5cf0ed2d6cbc5>` |
| 385 |
|
| 386 |
September 3, 2024 - :cve:`2024-45231` |
| 387 |
------------------------------------- |
| 388 |
|
| 389 |
Potential user email enumeration via response status on password reset. |
| 390 |
`Full description |
| 391 |
<https://www.djangoproject.com/weblog/2024/sep/03/security-releases/>`__ |
| 392 |
|
| 393 |
* Django 5.1 :commit:`(patch) <3c733c78d6f8e50296d6e248968b6516c92a53ca>` |
| 394 |
* Django 5.0 :commit:`(patch) <96d84047715ea1715b4bd1594e46122b8a77b9e2>` |
| 395 |
* Django 4.2 :commit:`(patch) <bf4888d317ba4506d091eeac6e8b4f1fcc731199>` |
| 396 |
|
| 397 |
September 3, 2024 - :cve:`2024-45230` |
| 398 |
------------------------------------- |
| 399 |
|
| 400 |
Potential denial-of-service vulnerability in ``django.utils.html.urlize()``. |
| 401 |
`Full description |
| 402 |
<https://www.djangoproject.com/weblog/2024/sep/03/security-releases/>`__ |
| 403 |
|
| 404 |
* Django 5.1 :commit:`(patch) <022ab0a75c76ab2ea31dfcc5f2cf5501e378d397>` |
| 405 |
* Django 5.0 :commit:`(patch) <813de2672bd7361e9a453ab62cd6e52f96b6525b>` |
| 406 |
* Django 4.2 :commit:`(patch) <d147a8ebbdf28c17cafbbe2884f0bc57e2bf82e2>` |
| 407 |
|
| 408 |
August 6, 2024 - :cve:`2024-42005` |
| 409 |
---------------------------------- |
| 410 |
|
| 411 |
Potential SQL injection in ``QuerySet.values()`` and ``values_list()``. |
| 412 |
`Full description |
| 413 |
<https://www.djangoproject.com/weblog/2024/aug/06/security-releases/>`__ |
| 414 |
|
| 415 |
* Django 5.0 :commit:`(patch) <32ebcbf2e1fe3e5ba79a6554a167efce81f7422d>` |
| 416 |
* Django 4.2 :commit:`(patch) <f4af67b9b41e0f4c117a8741da3abbd1c869ab28>` |
| 417 |
|
| 418 |
August 6, 2024 - :cve:`2024-41991` |
| 419 |
---------------------------------- |
| 420 |
|
| 421 |
Potential denial-of-service vulnerability in ``django.utils.html.urlize()`` and |
| 422 |
``AdminURLFieldWidget``. `Full description |
| 423 |
<https://www.djangoproject.com/weblog/2024/aug/06/security-releases/>`__ |
| 424 |
|
| 425 |
* Django 5.0 :commit:`(patch) <523da8771bce321023f490f70d71a9e973ddc927>` |
| 426 |
* Django 4.2 :commit:`(patch) <efea1ef7e2190e3f77ca0651b5458297bc0f6a9f>` |
| 427 |
|
| 428 |
August 6, 2024 - :cve:`2024-41990` |
| 429 |
---------------------------------- |
| 430 |
|
| 431 |
Potential denial-of-service vulnerability in ``django.utils.html.urlize()``. |
| 432 |
`Full description |
| 433 |
<https://www.djangoproject.com/weblog/2024/aug/06/security-releases/>`__ |
| 434 |
|
| 435 |
* Django 5.0 :commit:`(patch) <7b7b909579c8311c140c89b8a9431bf537febf93>` |
| 436 |
* Django 4.2 :commit:`(patch) <d0a82e26a74940bf0c78204933c3bdd6a283eb88>` |
| 437 |
|
| 438 |
August 6, 2024 - :cve:`2024-41989` |
| 439 |
---------------------------------- |
| 440 |
|
| 441 |
Potential memory exhaustion in ``django.utils.numberformat.floatformat()``. |
| 442 |
`Full description |
| 443 |
<https://www.djangoproject.com/weblog/2024/aug/06/security-releases/>`__ |
| 444 |
|
| 445 |
* Django 5.0 :commit:`(patch) <27900fe56f3d3cabb4aeb6ccb82f92bab29073a8>` |
| 446 |
* Django 4.2 :commit:`(patch) <fc76660f589ac07e45e9cd34ccb8087aeb11904b>` |
| 447 |
|
| 448 |
July 9, 2024 - :cve:`2024-39614` |
| 449 |
-------------------------------- |
| 450 |
|
| 451 |
Potential denial-of-service in |
| 452 |
``django.utils.translation.get_supported_language_variant()``. |
| 453 |
`Full description |
| 454 |
<https://www.djangoproject.com/weblog/2024/jul/09/security-releases/>`__ |
| 455 |
|
| 456 |
* Django 5.0 :commit:`(patch) <8e7a44e4bec0f11474699c3111a5e0a45afe7f49>` |
| 457 |
* Django 4.2 :commit:`(patch) <17358fb35fb7217423d4c4877ccb6d1a3a40b1c3>` |
| 458 |
|
| 459 |
July 9, 2024 - :cve:`2024-39330` |
| 460 |
-------------------------------- |
| 461 |
|
| 462 |
Potential directory-traversal in ``django.core.files.storage.Storage.save()``. |
| 463 |
`Full description |
| 464 |
<https://www.djangoproject.com/weblog/2024/jul/09/security-releases/>`__ |
| 465 |
|
| 466 |
* Django 5.0 :commit:`(patch) <9f4f63e9ebb7bf6cb9547ee4e2526b9b96703270>` |
| 467 |
* Django 4.2 :commit:`(patch) <2b00edc0151a660d1eb86da4059904a0fc4e095e>` |
| 468 |
|
| 469 |
July 9, 2024 - :cve:`2024-39329` |
| 470 |
-------------------------------- |
| 471 |
|
| 472 |
Username enumeration through timing difference for users with unusable |
| 473 |
passwords. `Full description |
| 474 |
<https://www.djangoproject.com/weblog/2024/jul/09/security-releases/>`__ |
| 475 |
|
| 476 |
* Django 5.0 :commit:`(patch) <07cefdee4a9d1fcd9a3a631cbd07c78defd1923b>` |
| 477 |
* Django 4.2 :commit:`(patch) <156d3186c96e3ec2ca73b8b25dc2ef366e38df14>` |
| 478 |
|
| 479 |
July 9, 2024 - :cve:`2024-38875` |
| 480 |
-------------------------------- |
| 481 |
|
| 482 |
Potential denial-of-service in ``django.utils.html.urlize()``. |
| 483 |
`Full description |
| 484 |
<https://www.djangoproject.com/weblog/2024/jul/09/security-releases/>`__ |
| 485 |
|
| 486 |
* Django 5.0 :commit:`(patch) <7285644640f085f41d60ab0c8ae4e9153f0485db>` |
| 487 |
* Django 4.2 :commit:`(patch) <79f368764295df109a37192f6182fb6f361d85b5>` |
| 488 |
|
| 489 |
March 4, 2024 - :cve:`2024-27351` |
| 490 |
--------------------------------- |
| 491 |
|
| 492 |
Potential regular expression denial-of-service in |
| 493 |
``django.utils.text.Truncator.words()``. `Full description |
| 494 |
<https://www.djangoproject.com/weblog/2024/mar/04/security-releases/>`__ |
| 495 |
|
| 496 |
* Django 5.0 :commit:`(patch) <3394fc6132436eca89e997083bae9985fb7e761e>` |
| 497 |
* Django 4.2 :commit:`(patch) <3c9a2771cc80821e041b16eb36c1c37af5349d4a>` |
| 498 |
* Django 3.2 :commit:`(patch) <072963e4c4d0b3a7a8c5412bc0c7d27d1a9c3521>` |
| 499 |
|
| 500 |
February 6, 2024 - :cve:`2024-24680` |
| 501 |
------------------------------------ |
| 502 |
|
| 503 |
Potential denial-of-service in ``intcomma`` template filter. |
| 504 |
`Full description |
| 505 |
<https://www.djangoproject.com/weblog/2024/feb/06/security-releases/>`__ |
| 506 |
|
| 507 |
* Django 5.0 :commit:`(patch) <16a8fe18a3b81250f4fa57e3f93f0599dc4895bc>` |
| 508 |
* Django 4.2 :commit:`(patch) <572ea07e84b38ea8de0551f4b4eda685d91d09d2>` |
| 509 |
* Django 3.2 :commit:`(patch) <c1171ffbd570db90ca206c30f8e2b9f691243820>` |
| 510 |
|
| 511 |
November 1, 2023 - :cve:`2023-46695` |
| 512 |
------------------------------------ |
| 513 |
|
| 514 |
Potential denial of service vulnerability in ``UsernameField`` on Windows. |
| 515 |
`Full description |
| 516 |
<https://www.djangoproject.com/weblog/2023/nov/01/security-releases/>`__ |
| 517 |
|
| 518 |
* Django 4.2 :commit:`(patch) <048a9ebb6ea468426cb4e57c71572cbbd975517f>` |
| 519 |
* Django 4.1 :commit:`(patch) <4965bfdde2e5a5c883685019e57d123a3368a75e>` |
| 520 |
* Django 3.2 :commit:`(patch) <f9a7fb8466a7ba4857eaf930099b5258f3eafb2b>` |
| 521 |
|
| 522 |
October 4, 2023 - :cve:`2023-43665` |
| 523 |
----------------------------------- |
| 524 |
|
| 525 |
Denial-of-service possibility in ``django.utils.text.Truncator``. |
| 526 |
`Full description |
| 527 |
<https://www.djangoproject.com/weblog/2023/oct/04/security-releases/>`__ |
| 528 |
|
| 529 |
* Django 4.2 :commit:`(patch) <be9c27c4d18c2e6a5be8af4e53c0797440794473>` |
| 530 |
* Django 4.1 :commit:`(patch) <c7b7024742250414e426ad49fb80db943e7ba4e8>` |
| 531 |
* Django 3.2 :commit:`(patch) <ccdade1a0262537868d7ca64374de3d957ca50c5>` |
| 532 |
|
| 533 |
September 4, 2023 - :cve:`2023-41164` |
| 534 |
------------------------------------- |
| 535 |
|
| 536 |
Potential denial of service vulnerability in |
| 537 |
``django.utils.encoding.uri_to_iri()``. `Full description |
| 538 |
<https://www.djangoproject.com/weblog/2023/sep/04/security-releases/>`__ |
| 539 |
|
| 540 |
* Django 4.2 :commit:`(patch) <9c51b4dcfa0cefcb48231f4d71cafa80821f87b9>` |
| 541 |
* Django 4.1 :commit:`(patch) <ba00bc5ec6a7eff5e08be438f7b5b0e9574e8ff0>` |
| 542 |
* Django 3.2 :commit:`(patch) <6f030b1149bd8fa4ba90452e77cb3edc095ce54e>` |
| 543 |
|
| 544 |
July 3, 2023 - :cve:`2023-36053` |
| 545 |
-------------------------------- |
| 546 |
|
| 547 |
Potential regular expression denial of service vulnerability in |
| 548 |
``EmailValidator``/``URLValidator``. `Full description |
| 549 |
<https://www.djangoproject.com/weblog/2023/jul/03/security-releases/>`__ |
| 550 |
|
| 551 |
* Django 4.2 :commit:`(patch) <b7c5feb35a31799de6e582ad6a5a91a9de74e0f9>` |
| 552 |
* Django 4.1 :commit:`(patch) <beb3f3d55940d9aa7198bf9d424ab74e873aec3d>` |
| 553 |
* Django 3.2 :commit:`(patch) <454f2fb93437f98917283336201b4048293f7582>` |
| 554 |
|
| 555 |
May 3, 2023 - :cve:`2023-31047` |
| 556 |
------------------------------- |
| 557 |
|
| 558 |
Potential bypass of validation when uploading multiple files using one form |
| 559 |
field. `Full description |
| 560 |
<https://www.djangoproject.com/weblog/2023/may/03/security-releases/>`__ |
| 561 |
|
| 562 |
* Django 4.2 :commit:`(patch) <21b1b1fc03e5f9e9f8c977ee6e35618dd3b353dd>` |
| 563 |
* Django 4.1 :commit:`(patch) <e7c3a2ccc3a562328600be05068ed9149e12ce64>` |
| 564 |
* Django 3.2 :commit:`(patch) <eed53d0011622e70b936e203005f0e6f4ac48965>` |
| 565 |
|
| 566 |
February 14, 2023 - :cve:`2023-24580` |
| 567 |
------------------------------------- |
| 568 |
|
| 569 |
Potential denial-of-service vulnerability in file uploads. `Full description |
| 570 |
<https://www.djangoproject.com/weblog/2023/feb/14/security-releases/>`__ |
| 571 |
|
| 572 |
* Django 4.1 :commit:`(patch) <628b33a854a9c68ec8a0c51f382f304a0044ec92>` |
| 573 |
* Django 4.0 :commit:`(patch) <83f1ea83e4553e211c1c5a0dfc197b66d4e50432>` |
| 574 |
* Django 3.2 :commit:`(patch) <a665ed5179f5bbd3db95ce67286d0192eff041d8>` |
| 575 |
|
| 576 |
February 1, 2023 - :cve:`2023-23969` |
| 577 |
------------------------------------ |
| 578 |
|
| 579 |
Potential denial-of-service via ``Accept-Language`` headers. `Full description |
| 580 |
<https://www.djangoproject.com/weblog/2023/feb/01/security-releases/>`__ |
| 581 |
|
| 582 |
* Django 4.1 :commit:`(patch) <9d7bd5a56b1ce0576e8e07a8001373576d277942>` |
| 583 |
* Django 4.0 :commit:`(patch) <4452642f193533e288a52c02efb5bbc766a68f95>` |
| 584 |
* Django 3.2 :commit:`(patch) <c7e0151fdf33e1b11d488b6f67b94fdf3a30614a>` |
| 585 |
|
| 586 |
October 4, 2022 - :cve:`2022-41323` |
| 587 |
----------------------------------- |
| 588 |
|
| 589 |
Potential denial-of-service vulnerability in internationalized URLs. `Full |
| 590 |
description |
| 591 |
<https://www.djangoproject.com/weblog/2022/oct/04/security-releases/>`__ |
| 592 |
|
| 593 |
* Django 4.1 :commit:`(patch) <9d656ea51d9ea7105c0c0785783ac29d426a7d25>` |
| 594 |
* Django 4.0 :commit:`(patch) <23f0093125ac2e553da6c1b2f9988eb6a3dd2ea1>` |
| 595 |
* Django 3.2 :commit:`(patch) <5b6b257fa7ec37ff27965358800c67e2dd11c924>` |
| 596 |
|
| 597 |
August 3, 2022 - :cve:`2022-36359` |
| 598 |
---------------------------------- |
| 599 |
|
| 600 |
Potential reflected file download vulnerability in FileResponse. `Full |
| 601 |
description |
| 602 |
<https://www.djangoproject.com/weblog/2022/aug/03/security-releases/>`__ |
| 603 |
|
| 604 |
* Django 4.0 :commit:`(patch) <b7d9529cbe0af4adabb6ea5d01ed8dcce3668fb3>` |
| 605 |
* Django 3.2 :commit:`(patch) <b3e4494d759202a3b6bf247fd34455bf13be5b80>` |
| 606 |
|
| 607 |
July 4, 2022 - :cve:`2022-34265` |
| 608 |
-------------------------------- |
| 609 |
|
| 610 |
Potential SQL injection via ``Trunc(kind)`` and ``Extract(lookup_name)`` |
| 611 |
arguments. `Full description |
| 612 |
<https://www.djangoproject.com/weblog/2022/jul/04/security-releases/>`__ |
| 613 |
|
| 614 |
* Django 4.0 :commit:`(patch) <0dc9c016fadb71a067e5a42be30164e3f96c0492>` |
| 615 |
* Django 3.2 :commit:`(patch) <a9010fe5555e6086a9d9ae50069579400ef0685e>` |
| 616 |
|
| 617 |
April 11, 2022 - :cve:`2022-28346` |
| 618 |
---------------------------------- |
| 619 |
|
| 620 |
Potential SQL injection in ``QuerySet.annotate()``, ``aggregate()``, and |
| 621 |
``extra()``. `Full description |
| 622 |
<https://www.djangoproject.com/weblog/2022/apr/11/security-releases/>`__ |
| 623 |
|
| 624 |
* Django 4.0 :commit:`(patch) <800828887a0509ad1162d6d407e94d8de7eafc60>` |
| 625 |
* Django 3.2 :commit:`(patch) <2044dac5c6968441be6f534c4139bcf48c5c7e48>` |
| 626 |
* Django 2.2 :commit:`(patch) <2c09e68ec911919360d5f8502cefc312f9e03c5d>` |
| 627 |
|
| 628 |
April 11, 2022 - :cve:`2022-28347` |
| 629 |
---------------------------------- |
| 630 |
|
| 631 |
Potential SQL injection via ``QuerySet.explain(**options)`` on PostgreSQL. |
| 632 |
`Full description |
| 633 |
<https://www.djangoproject.com/weblog/2022/apr/11/security-releases/>`__ |
| 634 |
|
| 635 |
* Django 4.0 :commit:`(patch) <00b0fc50e1738c7174c495464a5ef069408a4402>` |
| 636 |
* Django 3.2 :commit:`(patch) <9e19accb6e0a00ba77d5a95a91675bf18877c72d>` |
| 637 |
* Django 2.2 :commit:`(patch) <29a6c98b4c13af82064f993f0acc6e8fafa4d3f5>` |
| 638 |
|
| 639 |
February 1, 2022 - :cve:`2022-22818` |
| 640 |
------------------------------------ |
| 641 |
|
| 642 |
Possible XSS via ``{% debug %}`` template tag. `Full description |
| 643 |
<https://www.djangoproject.com/weblog/2022/feb/01/security-releases/>`__ |
| 644 |
|
| 645 |
Versions affected |
| 646 |
~~~~~~~~~~~~~~~~~ |
| 647 |
|
| 648 |
* Django 4.0 :commit:`(patch) <01422046065d2b51f8f613409cad2c81b39487e5>` |
| 649 |
* Django 3.2 :commit:`(patch) <1a1e8278c46418bde24c86a65443b0674bae65e2>` |
| 650 |
* Django 2.2 :commit:`(patch) <c27a7eb9f40b64990398978152e62b6ff839c2e6>` |
| 651 |
|
| 652 |
February 1, 2022 - :cve:`2022-23833` |
| 653 |
------------------------------------ |
| 654 |
|
| 655 |
Denial-of-service possibility in file uploads. `Full description |
| 656 |
<https://www.djangoproject.com/weblog/2022/feb/01/security-releases/>`__ |
| 657 |
|
| 658 |
Versions affected |
| 659 |
~~~~~~~~~~~~~~~~~ |
| 660 |
|
| 661 |
* Django 4.0 :commit:`(patch) <f9c7d48fdd6f198a6494a9202f90242f176e4fc9>` |
| 662 |
* Django 3.2 :commit:`(patch) <d16133568ef9c9b42cb7a08bdf9ff3feec2e5468>` |
| 663 |
* Django 2.2 :commit:`(patch) <c477b761804984c932704554ad35f78a2e230c6a>` |
| 664 |
|
| 665 |
January 4, 2022 - :cve:`2021-45452` |
| 666 |
------------------------------------ |
| 667 |
|
| 668 |
Potential directory-traversal via ``Storage.save()``. `Full description |
| 669 |
<https://www.djangoproject.com/weblog/2022/jan/04/security-releases/>`__ |
| 670 |
|
| 671 |
Versions affected |
| 672 |
~~~~~~~~~~~~~~~~~ |
| 673 |
|
| 674 |
* Django 4.0 :commit:`(patch) <e1592e0f26302e79856cc7f2218ae848ae19b0f6>` |
| 675 |
* Django 3.2 :commit:`(patch) <8d2f7cff76200cbd2337b2cf1707e383eb1fb54b>` |
| 676 |
* Django 2.2 :commit:`(patch) <4cb35b384ceef52123fc66411a73c36a706825e1>` |
| 677 |
|
| 678 |
January 4, 2022 - :cve:`2021-45116` |
| 679 |
------------------------------------ |
| 680 |
|
| 681 |
Potential information disclosure in ``dictsort`` template filter. `Full |
| 682 |
description |
| 683 |
<https://www.djangoproject.com/weblog/2022/jan/04/security-releases/>`__ |
| 684 |
|
| 685 |
Versions affected |
| 686 |
~~~~~~~~~~~~~~~~~ |
| 687 |
|
| 688 |
* Django 4.0 :commit:`(patch) <2a8ec7f546d6d5806e221ec948c5146b55bd7489>` |
| 689 |
* Django 3.2 :commit:`(patch) <c7fe895bca06daf12cc1670b56eaf72a1ef27a16>` |
| 690 |
* Django 2.2 :commit:`(patch) <c9f648ccfac5ab90fb2829a66da4f77e68c7f93a>` |
| 691 |
|
| 692 |
January 4, 2022 - :cve:`2021-45115` |
| 693 |
------------------------------------ |
| 694 |
|
| 695 |
Denial-of-service possibility in ``UserAttributeSimilarityValidator``. `Full |
| 696 |
description |
| 697 |
<https://www.djangoproject.com/weblog/2022/jan/04/security-releases/>`__ |
| 698 |
|
| 699 |
Versions affected |
| 700 |
~~~~~~~~~~~~~~~~~ |
| 701 |
|
| 702 |
* Django 4.0 :commit:`(patch) <df79ef03ac867c93caaa6be56bc69e66abfeef8f>` |
| 703 |
* Django 3.2 :commit:`(patch) <a8b32fe13bcaed1c0b772fdc53de84abc224fb20>` |
| 704 |
* Django 2.2 :commit:`(patch) <2135637fdd5ce994de110affef9e67dffdf77277>` |
| 705 |
|
| 706 |
December 7, 2021 - :cve:`2021-44420` |
| 707 |
------------------------------------ |
| 708 |
|
| 709 |
Potential bypass of an upstream access control based on URL paths. `Full |
| 710 |
description |
| 711 |
<https://www.djangoproject.com/weblog/2021/dec/07/security-releases/>`__ |
| 712 |
|
| 713 |
Versions affected |
| 714 |
~~~~~~~~~~~~~~~~~ |
| 715 |
|
| 716 |
* Django 3.2 :commit:`(patch) <333c65603032c377e682cdbd7388657a5463a05a>` |
| 717 |
* Django 3.1 :commit:`(patch) <22bd17488159601bf0741b70ae7932bffea8eced>` |
| 718 |
* Django 2.2 :commit:`(patch) <7cf7d74e8a754446eeb85cacf2fef1247e0cb6d7>` |
| 719 |
|
| 720 |
July 1, 2021 - :cve:`2021-35042` |
| 721 |
-------------------------------- |
| 722 |
|
| 723 |
Potential SQL injection via unsanitized ``QuerySet.order_by()`` input. `Full |
| 724 |
description |
| 725 |
<https://www.djangoproject.com/weblog/2021/jul/01/security-releases/>`__ |
| 726 |
|
| 727 |
Versions affected |
| 728 |
~~~~~~~~~~~~~~~~~ |
| 729 |
|
| 730 |
* Django 3.2 :commit:`(patch) <a34a5f724c5d5adb2109374ba3989ebb7b11f81f>` |
| 731 |
* Django 3.1 :commit:`(patch) <0bd57a879a0d54920bb9038a732645fb917040e9>` |
| 732 |
|
| 733 |
June 2, 2021 - :cve:`2021-33203` |
| 734 |
-------------------------------- |
| 735 |
|
| 736 |
Potential directory traversal via ``admindocs``. `Full description |
| 737 |
<https://www.djangoproject.com/weblog/2021/jun/02/security-releases/>`__ |
| 738 |
|
| 739 |
Versions affected |
| 740 |
~~~~~~~~~~~~~~~~~ |
| 741 |
|
| 742 |
* Django 3.2 :commit:`(patch) <dfaba12cda060b8b292ae1d271b44bf810b1c5b9>` |
| 743 |
* Django 3.1 :commit:`(patch) <20c67a0693c4ede2b09af02574823485e82e4c8f>` |
| 744 |
* Django 2.2 :commit:`(patch) <053cc9534d174dc89daba36724ed2dcb36755b90>` |
| 745 |
|
| 746 |
June 2, 2021 - :cve:`2021-33571` |
| 747 |
-------------------------------- |
| 748 |
|
| 749 |
Possible indeterminate SSRF, RFI, and LFI attacks since validators accepted |
| 750 |
leading zeros in IPv4 addresses. `Full description |
| 751 |
<https://www.djangoproject.com/weblog/2021/jun/02/security-releases/>`__ |
| 752 |
|
| 753 |
Versions affected |
| 754 |
~~~~~~~~~~~~~~~~~ |
| 755 |
|
| 756 |
* Django 3.2 :commit:`(patch) <9f75e2e562fa0c0482f3dde6fc7399a9070b4a3d>` |
| 757 |
* Django 3.1 :commit:`(patch) <203d4ab9ebcd72fc4d6eb7398e66ed9e474e118e>` |
| 758 |
* Django 2.2 :commit:`(patch) <f27c38ab5d90f68c9dd60cabef248a570c0be8fc>` |
| 759 |
|
| 760 |
May 6, 2021 - :cve:`2021-32052` |
| 761 |
------------------------------- |
| 762 |
|
| 763 |
Header injection possibility since ``URLValidator`` accepted newlines in input |
| 764 |
on Python 3.9.5+. `Full description |
| 765 |
<https://www.djangoproject.com/weblog/2021/may/06/security-releases/>`__ |
| 766 |
|
| 767 |
Versions affected |
| 768 |
~~~~~~~~~~~~~~~~~ |
| 769 |
|
| 770 |
* Django 3.2 :commit:`(patch) <2d2c1d0c97832860fbd6597977e2aae17dd7e5b2>` |
| 771 |
* Django 3.1 :commit:`(patch) <afb23f5929944a407e4990edef1c7806a94c9879>` |
| 772 |
* Django 2.2 :commit:`(patch) <d9594c4ea57b6309d93879805302cec9ae9f23ff>` |
| 773 |
|
| 774 |
May 4, 2021 - :cve:`2021-31542` |
| 775 |
------------------------------- |
| 776 |
|
| 777 |
Potential directory-traversal via uploaded files. `Full description |
| 778 |
<https://www.djangoproject.com/weblog/2021/may/04/security-releases/>`__ |
| 779 |
|
| 780 |
Versions affected |
| 781 |
~~~~~~~~~~~~~~~~~ |
| 782 |
|
| 783 |
* Django 3.2 :commit:`(patch) <c98f446c188596d4ba6de71d1b77b4a6c5c2a007>` |
| 784 |
* Django 3.1 :commit:`(patch) <25d84d64122c15050a0ee739e859f22ddab5ac48>` |
| 785 |
* Django 2.2 :commit:`(patch) <04ac1624bdc2fa737188401757cf95ced122d26d>` |
| 786 |
|
| 787 |
April 6, 2021 - :cve:`2021-28658` |
| 788 |
--------------------------------- |
| 789 |
|
| 790 |
Potential directory-traversal via uploaded files. `Full description |
| 791 |
<https://www.djangoproject.com/weblog/2021/apr/06/security-releases/>`__ |
| 792 |
|
| 793 |
Versions affected |
| 794 |
~~~~~~~~~~~~~~~~~ |
| 795 |
|
| 796 |
* Django 3.2 :commit:`(patch) <2820fd1be5dfccbf1216c3845fad8580502473e1>` |
| 797 |
* Django 3.1 :commit:`(patch) <cca0d98118cccf9ae0c6dcf2d6c57fc50469fbf0>` |
| 798 |
* Django 3.0 :commit:`(patch) <e7fba62248f604c76da4f23dcf1db4a57b0808ea>` |
| 799 |
* Django 2.2 :commit:`(patch) <4036d62bda0e9e9f6172943794b744a454ca49c2>` |
| 800 |
|
| 801 |
February 19, 2021 - :cve:`2021-23336` |
| 802 |
------------------------------------- |
| 803 |
|
| 804 |
Web cache poisoning via ``django.utils.http.limited_parse_qsl()``. `Full |
| 805 |
description |
| 806 |
<https://www.djangoproject.com/weblog/2021/feb/19/security-releases/>`__ |
| 807 |
|
| 808 |
Versions affected |
| 809 |
~~~~~~~~~~~~~~~~~ |
| 810 |
|
| 811 |
* Django 3.2 :commit:`(patch) <be8237c7cce24b06aabde0b97afce98ddabbe3b6>` |
| 812 |
* Django 3.1 :commit:`(patch) <8f6d431b08cbb418d9144b976e7b972546607851>` |
| 813 |
* Django 3.0 :commit:`(patch) <326a926beef869d3341bc9ef737887f0449b6b71>` |
| 814 |
* Django 2.2 :commit:`(patch) <fd6b6afd5959b638c62dbf4839ccff97e7f7dfda>` |
| 815 |
|
| 816 |
February 1, 2021 - :cve:`2021-3281` |
| 817 |
----------------------------------- |
| 818 |
|
| 819 |
Potential directory-traversal via ``archive.extract()``. `Full description |
| 820 |
<https://www.djangoproject.com/weblog/2021/feb/01/security-releases/>`__ |
| 821 |
|
| 822 |
Versions affected |
| 823 |
~~~~~~~~~~~~~~~~~ |
| 824 |
|
| 825 |
* Django 3.1 :commit:`(patch) <02e6592835b4559909aa3aaaf67988fef435f624>` |
| 826 |
* Django 3.0 :commit:`(patch) <52e409ed17287e9aabda847b6afe58be2fa9f86a>` |
| 827 |
* Django 2.2 :commit:`(patch) <21e7622dec1f8612c85c2fc37fe8efbfd3311e37>` |
| 828 |
|
| 829 |
September 1, 2020 - :cve:`2020-24584` |
| 830 |
------------------------------------- |
| 831 |
|
| 832 |
Permission escalation in intermediate-level directories of the file system |
| 833 |
cache on Python 3.7+. `Full description |
| 834 |
<https://www.djangoproject.com/weblog/2020/sep/01/security-releases/>`__ |
| 835 |
|
| 836 |
Versions affected |
| 837 |
~~~~~~~~~~~~~~~~~ |
| 838 |
|
| 839 |
* Django 3.1 :commit:`(patch) <2b099caa5923afa8cfb5f1e8c0d56b6e0e81915b>` |
| 840 |
* Django 3.0 :commit:`(patch) <cdb367c92a0ba72ddc0cbd13ff42b0e6df709554>` |
| 841 |
* Django 2.2 :commit:`(patch) <a3aebfdc8153dc230686b6d2454ccd32ed4c9e6f>` |
| 842 |
|
| 843 |
September 1, 2020 - :cve:`2020-24583` |
| 844 |
------------------------------------- |
| 845 |
|
| 846 |
Incorrect permissions on intermediate-level directories on Python 3.7+. `Full |
| 847 |
description |
| 848 |
<https://www.djangoproject.com/weblog/2020/sep/01/security-releases/>`__ |
| 849 |
|
| 850 |
Versions affected |
| 851 |
~~~~~~~~~~~~~~~~~ |
| 852 |
|
| 853 |
* Django 3.1 :commit:`(patch) <934430d22aa5d90c2ba33495ff69a6a1d997d584>` |
| 854 |
* Django 3.0 :commit:`(patch) <08892bffd275c79ee1f8f67639eb170aaaf1181e>` |
| 855 |
* Django 2.2 :commit:`(patch) <375657a71c889c588f723469bd868bd1d40c369f>` |
| 856 |
|
| 857 |
June 3, 2020 - :cve:`2020-13596` |
| 858 |
-------------------------------- |
| 859 |
|
| 860 |
Possible XSS via admin ``ForeignKeyRawIdWidget``. `Full description |
| 861 |
<https://www.djangoproject.com/weblog/2020/jun/03/security-releases/>`__ |
| 862 |
|
| 863 |
Versions affected |
| 864 |
~~~~~~~~~~~~~~~~~ |
| 865 |
|
| 866 |
* Django 3.0 :commit:`(patch) <1f2dd37f6fcefdd10ed44cb233b2e62b520afb38>` |
| 867 |
* Django 2.2 :commit:`(patch) <6d61860b22875f358fac83d903dc629897934815>` |
| 868 |
|
| 869 |
June 3, 2020 - :cve:`2020-13254` |
| 870 |
-------------------------------- |
| 871 |
|
| 872 |
Potential data leakage via malformed memcached keys. `Full description |
| 873 |
<https://www.djangoproject.com/weblog/2020/jun/03/security-releases/>`__ |
| 874 |
|
| 875 |
Versions affected |
| 876 |
~~~~~~~~~~~~~~~~~ |
| 877 |
|
| 878 |
* Django 3.0 :commit:`(patch) <84b2da5552e100ae3294f564f6c862fef8d0e693>` |
| 879 |
* Django 2.2 :commit:`(patch) <07e59caa02831c4569bbebb9eb773bdd9cb4b206>` |
| 880 |
|
| 881 |
March 4, 2020 - :cve:`2020-9402` |
| 882 |
-------------------------------- |
| 883 |
|
| 884 |
Potential SQL injection via ``tolerance`` parameter in GIS functions and |
| 885 |
aggregates on Oracle. `Full description |
| 886 |
<https://www.djangoproject.com/weblog/2020/mar/04/security-releases/>`__ |
| 887 |
|
| 888 |
Versions affected |
| 889 |
~~~~~~~~~~~~~~~~~ |
| 890 |
|
| 891 |
* Django 3.0 :commit:`(patch) <26a5cf834526e291db00385dd33d319b8271fc4c>` |
| 892 |
* Django 2.2 :commit:`(patch) <fe886a3b58a93cfbe8864b485f93cb6d426cd1f2>` |
| 893 |
* Django 1.11 :commit:`(patch) <02d97f3c9a88adc890047996e5606180bd1c6166>` |
| 894 |
|
| 895 |
February 3, 2020 - :cve:`2020-7471` |
| 896 |
----------------------------------- |
| 897 |
|
| 898 |
Potential SQL injection via ``StringAgg(delimiter)``. `Full description |
| 899 |
<https://www.djangoproject.com/weblog/2020/feb/03/security-releases/>`__ |
| 900 |
|
| 901 |
Versions affected |
| 902 |
~~~~~~~~~~~~~~~~~ |
| 903 |
|
| 904 |
* Django 3.0 :commit:`(patch) <505826b469b16ab36693360da9e11fd13213421b>` |
| 905 |
* Django 2.2 :commit:`(patch) <c67a368c16e4680b324b4f385398d638db4d8147>` |
| 906 |
* Django 1.11 :commit:`(patch) <001b0634cd309e372edb6d7d95d083d02b8e37bd>` |
| 907 |
|
| 908 |
December 18, 2019 - :cve:`2019-19844` |
| 909 |
------------------------------------- |
| 910 |
|
| 911 |
Potential account hijack via password reset form. `Full description |
| 912 |
<https://www.djangoproject.com/weblog/2019/dec/18/security-releases/>`__ |
| 913 |
|
| 914 |
Versions affected |
| 915 |
~~~~~~~~~~~~~~~~~ |
| 916 |
|
| 917 |
* Django 3.0 :commit:`(patch) <302a4ff1e8b1c798aab97673909c7a3dfda42c26>` |
| 918 |
* Django 2.2 :commit:`(patch) <4d334bea06cac63dc1272abcec545b85136cca0e>` |
| 919 |
* Django 1.11 :commit:`(patch) <f4cff43bf921fcea6a29b726eb66767f67753fa2>` |
| 920 |
|
| 921 |
December 2, 2019 - :cve:`2019-19118` |
| 922 |
------------------------------------ |
| 923 |
|
| 924 |
Privilege escalation in the Django admin. `Full description |
| 925 |
<https://www.djangoproject.com/weblog/2019/dec/02/security-releases/>`__ |
| 926 |
|
| 927 |
Versions affected |
| 928 |
~~~~~~~~~~~~~~~~~ |
| 929 |
|
| 930 |
* Django 3.0 :commit:`(patch) <092cd66cf3c3e175acce698d6ca2012068d878fa>` |
| 931 |
* Django 2.2 :commit:`(patch) <36f580a17f0b3cb087deadf3b65eea024f479c21>` |
| 932 |
* Django 2.1 :commit:`(patch) <103ebe2b5ff1b2614b85a52c239f471904d26244>` |
| 933 |
|
| 934 |
August 1, 2019 - :cve:`2019-14235` |
| 935 |
---------------------------------- |
| 936 |
|
| 937 |
Potential memory exhaustion in ``django.utils.encoding.uri_to_iri()``. `Full |
| 938 |
description |
| 939 |
<https://www.djangoproject.com/weblog/2019/aug/01/security-releases/>`__ |
| 940 |
|
| 941 |
Versions affected |
| 942 |
~~~~~~~~~~~~~~~~~ |
| 943 |
|
| 944 |
* Django 2.2 :commit:`(patch) <cf694e6852b0da7799f8b53f1fb2f7d20cf17534>` |
| 945 |
* Django 2.1 :commit:`(patch) <5d50a2e5fa36ad23ab532fc54cf4073de84b3306>` |
| 946 |
* Django 1.11 :commit:`(patch) <869b34e9b3be3a4cfcb3a145f218ffd3f5e3fd79>` |
| 947 |
|
| 948 |
August 1, 2019 - :cve:`2019-14234` |
| 949 |
---------------------------------- |
| 950 |
|
| 951 |
SQL injection possibility in key and index lookups for |
| 952 |
``JSONField``/``HStoreField``. `Full description |
| 953 |
<https://www.djangoproject.com/weblog/2019/aug/01/security-releases/>`__ |
| 954 |
|
| 955 |
Versions affected |
| 956 |
~~~~~~~~~~~~~~~~~ |
| 957 |
|
| 958 |
* Django 2.2 :commit:`(patch) <4f5b58f5cd3c57fee9972ab074f8dc6895d8f387>` |
| 959 |
* Django 2.1 :commit:`(patch) <f74b3ae3628c26e1b4f8db3d13a91d52a833a975>` |
| 960 |
* Django 1.11 :commit:`(patch) <ed682a24fca774818542757651bfba576c3fc3ef>` |
| 961 |
|
| 962 |
August 1, 2019 - :cve:`2019-14233` |
| 963 |
---------------------------------- |
| 964 |
|
| 965 |
Denial-of-service possibility in ``strip_tags()``. `Full description |
| 966 |
<https://www.djangoproject.com/weblog/2019/aug/01/security-releases/>`__ |
| 967 |
|
| 968 |
Versions affected |
| 969 |
~~~~~~~~~~~~~~~~~ |
| 970 |
|
| 971 |
* Django 2.2 :commit:`(patch) <e34f3c0e9ee5fc9022428fe91640638bafd4cda7>` |
| 972 |
* Django 2.1 :commit:`(patch) <5ff8e791148bd451180124d76a55cb2b2b9556eb>` |
| 973 |
* Django 1.11 :commit:`(patch) <52479acce792ad80bb0f915f20b835f919993c72>` |
| 974 |
|
| 975 |
|
| 976 |
August 1, 2019 - :cve:`2019-14232` |
| 977 |
---------------------------------- |
| 978 |
|
| 979 |
Denial-of-service possibility in ``django.utils.text.Truncator``. `Full |
| 980 |
description <https://www.djangoproject.com/weblog/2019/aug/01/security-releases/>`__ |
| 981 |
|
| 982 |
Versions affected |
| 983 |
~~~~~~~~~~~~~~~~~ |
| 984 |
|
| 985 |
* Django 2.2 :commit:`(patch) <c3289717c6f21a8cf23daff1c78c0c014b94041f>` |
| 986 |
* Django 2.1 :commit:`(patch) <c23723a1551340cc7d3126f04fcfd178fa224193>` |
| 987 |
* Django 1.11 :commit:`(patch) <42a66e969023c00536256469f0e8b8a099ef109d>` |
| 988 |
|
| 989 |
July 1, 2019 - :cve:`2019-12781` |
| 990 |
-------------------------------- |
| 991 |
|
| 992 |
Incorrect HTTP detection with reverse-proxy connecting via HTTPS. `Full |
| 993 |
description <https://www.djangoproject.com/weblog/2019/jul/01/security-releases/>`__ |
| 994 |
|
| 995 |
Versions affected |
| 996 |
~~~~~~~~~~~~~~~~~ |
| 997 |
|
| 998 |
* Django 2.2 :commit:`(patch) <77706a3e4766da5d5fb75c4db22a0a59a28e6cd6>` |
| 999 |
* Django 2.1 :commit:`(patch) <1e40f427bb8d0fb37cc9f830096a97c36c97af6f>` |
| 1000 |
* Django 1.11 :commit:`(patch) <32124fc41e75074141b05f10fc55a4f01ff7f050>` |
| 1001 |
|
| 1002 |
June 3, 2019 - :cve:`2019-12308` |
| 1003 |
-------------------------------- |
| 1004 |
|
| 1005 |
XSS via "Current URL" link generated by ``AdminURLFieldWidget``. `Full |
| 1006 |
description <https://www.djangoproject.com/weblog/2019/jun/03/security-releases/>`__ |
| 1007 |
|
| 1008 |
Versions affected |
| 1009 |
~~~~~~~~~~~~~~~~~ |
| 1010 |
|
| 1011 |
* Django 2.2 :commit:`(patch) <afddabf8428ddc89a332f7a78d0d21eaf2b5a673>` |
| 1012 |
* Django 2.1 :commit:`(patch) <09186a13d975de6d049f8b3e05484f66b01ece62>` |
| 1013 |
* Django 1.11 :commit:`(patch) <c238701859a52d584f349cce15d56c8e8137c52b>` |
| 1014 |
|
| 1015 |
June 3, 2019 - :cve:`2019-11358` |
| 1016 |
-------------------------------- |
| 1017 |
|
| 1018 |
Prototype pollution in bundled jQuery. `Full description |
| 1019 |
<https://www.djangoproject.com/weblog/2019/jun/03/security-releases/>`__ |
| 1020 |
|
| 1021 |
Versions affected |
| 1022 |
~~~~~~~~~~~~~~~~~ |
| 1023 |
|
| 1024 |
* Django 2.2 :commit:`(patch) <baaf187a4e354bf3976c51e2c83a0d2f8ee6e6ad>` |
| 1025 |
* Django 2.1 :commit:`(patch) <95649bc08547a878cebfa1d019edec8cb1b80829>` |
| 1026 |
|
| 1027 |
February 11, 2019 - :cve:`2019-6975` |
| 1028 |
------------------------------------ |
| 1029 |
|
| 1030 |
Memory exhaustion in ``django.utils.numberformat.format()``. `Full description |
| 1031 |
<https://www.djangoproject.com/weblog/2019/feb/11/security-releases/>`__ |
| 1032 |
|
| 1033 |
Versions affected |
| 1034 |
~~~~~~~~~~~~~~~~~ |
| 1035 |
|
| 1036 |
* Django 2.1 :commit:`(patch) <40cd19055773705301c3428ed5e08a036d2091f3>` |
| 1037 |
* Django 2.0 :commit:`(patch <1f42f82566c9d2d73aff1c42790d6b1b243f7676>` and |
| 1038 |
:commit:`correction) <392e040647403fc8007708d52ce01d915b014849>` |
| 1039 |
* Django 1.11 :commit:`(patch) <0bbb560183fabf0533289700845dafa94951f227>` |
| 1040 |
|
| 1041 |
January 4, 2019 - :cve:`2019-3498` |
| 1042 |
---------------------------------- |
| 1043 |
|
| 1044 |
Content spoofing possibility in the default 404 page. `Full description |
| 1045 |
<https://www.djangoproject.com/weblog/2019/jan/04/security-releases/>`__ |
| 1046 |
|
| 1047 |
Versions affected |
| 1048 |
~~~~~~~~~~~~~~~~~ |
| 1049 |
|
| 1050 |
* Django 2.1 :commit:`(patch) <64d2396e83aedba3fcc84ca40f23fbd22f0b9b5b>` |
| 1051 |
* Django 2.0 :commit:`(patch) <9f4ed7c94c62e21644ef5115e393ac426b886f2e>` |
| 1052 |
* Django 1.11 :commit:`(patch) <1cd00fcf52d089ef0fe03beabd05d59df8ea052a>` |
| 1053 |
|
| 1054 |
October 1, 2018 - :cve:`2018-16984` |
| 1055 |
----------------------------------- |
| 1056 |
|
| 1057 |
Password hash disclosure to "view only" admin users. `Full description |
| 1058 |
<https://www.djangoproject.com/weblog/2018/oct/01/security-release/>`__ |
| 1059 |
|
| 1060 |
Versions affected |
| 1061 |
~~~~~~~~~~~~~~~~~ |
| 1062 |
|
| 1063 |
* Django 2.1 :commit:`(patch) <c4bd5b597e0aa2432e4c867b86650f18af117851>` |
| 1064 |
|
| 1065 |
August 1, 2018 - :cve:`2018-14574` |
| 1066 |
---------------------------------- |
| 1067 |
|
| 1068 |
Open redirect possibility in ``CommonMiddleware``. `Full description |
| 1069 |
<https://www.djangoproject.com/weblog/2018/aug/01/security-releases/>`__ |
| 1070 |
|
| 1071 |
Versions affected |
| 1072 |
~~~~~~~~~~~~~~~~~ |
| 1073 |
|
| 1074 |
* Django 2.1 :commit:`(patch) <c4e5ff7fdb5fce447675e90291fd33fddd052b3c>` |
| 1075 |
* Django 2.0 :commit:`(patch) <6fffc3c6d420e44f4029d5643f38d00a39b08525>` |
| 1076 |
* Django 1.11 :commit:`(patch) <d6eaee092709aad477a9894598496c6deec532ff>` |
| 1077 |
|
| 1078 |
March 6, 2018 - :cve:`2018-7537` |
| 1079 |
-------------------------------- |
| 1080 |
|
| 1081 |
Denial-of-service possibility in ``truncatechars_html`` and |
| 1082 |
``truncatewords_html`` template filters. `Full description |
| 1083 |
<https://www.djangoproject.com/weblog/2018/mar/06/security-releases/>`__ |
| 1084 |
|
| 1085 |
Versions affected |
| 1086 |
~~~~~~~~~~~~~~~~~ |
| 1087 |
|
| 1088 |
* Django 2.0 :commit:`(patch) <94c5da1d17a6b0d378866c66b605102c19f7988c>` |
| 1089 |
* Django 1.11 :commit:`(patch) <a91436360b79a6ff995c3e5018bcc666dfaf1539>` |
| 1090 |
* Django 1.8 :commit:`(patch) <d17974a287a6ea2e361daff88fcc004cbd6835fa>` |
| 1091 |
|
| 1092 |
March 6, 2018 - :cve:`2018-7536` |
| 1093 |
-------------------------------- |
| 1094 |
|
| 1095 |
Denial-of-service possibility in ``urlize`` and ``urlizetrunc`` template |
| 1096 |
filters. `Full description |
| 1097 |
<https://www.djangoproject.com/weblog/2018/mar/06/security-releases/>`__ |
| 1098 |
|
| 1099 |
Versions affected |
| 1100 |
~~~~~~~~~~~~~~~~~ |
| 1101 |
|
| 1102 |
* Django 2.0 :commit:`(patch) <e157315da3ae7005fa0683ffc9751dbeca7306c8>` |
| 1103 |
* Django 1.11 :commit:`(patch) <abf89d729f210c692a50e0ad3f75fb6bec6fae16>` |
| 1104 |
* Django 1.8 :commit:`(patch) <1ca63a66ef3163149ad822701273e8a1844192c2>` |
| 1105 |
|
| 1106 |
February 1, 2018 - :cve:`2018-6188` |
| 1107 |
----------------------------------- |
| 1108 |
|
| 1109 |
Information leakage in ``AuthenticationForm``. `Full description |
| 1110 |
<https://www.djangoproject.com/weblog/2018/feb/01/security-releases/>`__ |
| 1111 |
|
| 1112 |
Versions affected |
| 1113 |
~~~~~~~~~~~~~~~~~ |
| 1114 |
|
| 1115 |
* Django 2.0 :commit:`(patch) <c37bb28677295f6edda61d8ac461014ef0d3aeb2>` |
| 1116 |
* Django 1.11 :commit:`(patch) <57b95fedad5e0b83fc9c81466b7d1751c6427aae>` |
| 1117 |
|
| 1118 |
September 5, 2017 - :cve:`2017-12794` |
| 1119 |
------------------------------------- |
| 1120 |
|
| 1121 |
Possible XSS in traceback section of technical 500 debug page. `Full |
| 1122 |
description <https://www.djangoproject.com/weblog/2017/sep/05/security-releases/>`__ |
| 1123 |
|
| 1124 |
Versions affected |
| 1125 |
~~~~~~~~~~~~~~~~~ |
| 1126 |
|
| 1127 |
* Django 1.11 :commit:`(patch) <e35a0c56086924f331e9422daa266e907a4784cc>` |
| 1128 |
* Django 1.10 :commit:`(patch) <58e08e80e362db79eb0fd775dc81faad90dca47a>` |
| 1129 |
|
| 1130 |
April 4, 2017 - :cve:`2017-7234` |
| 1131 |
-------------------------------- |
| 1132 |
|
| 1133 |
Open redirect vulnerability in ``django.views.static.serve()``. `Full |
| 1134 |
description <https://www.djangoproject.com/weblog/2017/apr/04/security-releases/>`__ |
| 1135 |
|
| 1136 |
Versions affected |
| 1137 |
~~~~~~~~~~~~~~~~~ |
| 1138 |
|
| 1139 |
* Django 1.10 :commit:`(patch) <2a9f6ef71b8e23fd267ee2be1be26dde8ab67037>` |
| 1140 |
* Django 1.9 :commit:`(patch) <5f1ffb07afc1e59729ce2b283124116d6c0659e4>` |
| 1141 |
* Django 1.8 :commit:`(patch) <4a6b945dffe8d10e7cec107d93e6efaebfbded29>` |
| 1142 |
|
| 1143 |
April 4, 2017 - :cve:`2017-7233` |
| 1144 |
-------------------------------- |
| 1145 |
|
| 1146 |
Open redirect and possible XSS attack via user-supplied numeric redirect URLs. |
| 1147 |
`Full description <https://www.djangoproject.com/weblog/2017/apr/04/security-releases/>`__ |
| 1148 |
|
| 1149 |
Versions affected |
| 1150 |
~~~~~~~~~~~~~~~~~ |
| 1151 |
|
| 1152 |
* Django 1.10 :commit:`(patch) <f824655bc2c50b19d2f202d7640785caabc82787>` |
| 1153 |
* Django 1.9 :commit:`(patch) <254326cb3682389f55f886804d2c43f7b9f23e4f>` |
| 1154 |
* Django 1.8 :commit:`(patch) <8339277518c7d8ec280070a780915304654e3b66>` |
| 1155 |
|
| 1156 |
November 1, 2016 - :cve:`2016-9014` |
| 1157 |
----------------------------------- |
| 1158 |
|
| 1159 |
DNS rebinding vulnerability when ``DEBUG=True``. `Full description |
| 1160 |
<https://www.djangoproject.com/weblog/2016/nov/01/security-releases/>`__ |
| 1161 |
|
| 1162 |
Versions affected |
| 1163 |
~~~~~~~~~~~~~~~~~ |
| 1164 |
|
| 1165 |
* Django 1.10 :commit:`(patch) <884e113838e5a72b4b0ec9e5e87aa480f6aa4472>` |
| 1166 |
* Django 1.9 :commit:`(patch) <45acd6d836895a4c36575f48b3fb36a3dae98d19>` |
| 1167 |
* Django 1.8 :commit:`(patch) <c401ae9a7dfb1a94a8a61927ed541d6f93089587>` |
| 1168 |
|
| 1169 |
November 1, 2016 - :cve:`2016-9013` |
| 1170 |
----------------------------------- |
| 1171 |
|
| 1172 |
User with hardcoded password created when running tests on Oracle. `Full |
| 1173 |
description <https://www.djangoproject.com/weblog/2016/nov/01/security-releases/>`__ |
| 1174 |
|
| 1175 |
Versions affected |
| 1176 |
~~~~~~~~~~~~~~~~~ |
| 1177 |
|
| 1178 |
* Django 1.10 :commit:`(patch) <34e10720d81b8d407aa14d763b6a7fe8f13b4f2e>` |
| 1179 |
* Django 1.9 :commit:`(patch) <4844d86c7728c1a5a3bbce4ad336a8d32304072b>` |
| 1180 |
* Django 1.8 :commit:`(patch) <70f99952965a430daf69eeb9947079aae535d2d0>` |
| 1181 |
|
| 1182 |
September 26, 2016 - :cve:`2016-7401` |
| 1183 |
------------------------------------- |
| 1184 |
|
| 1185 |
CSRF protection bypass on a site with Google Analytics. `Full description |
| 1186 |
<https://www.djangoproject.com/weblog/2016/sep/26/security-releases/>`__ |
| 1187 |
|
| 1188 |
Versions affected |
| 1189 |
~~~~~~~~~~~~~~~~~ |
| 1190 |
|
| 1191 |
* Django 1.9 :commit:`(patch) <d1bc980db1c0fffd6d60677e62f70beadb9fe64a>` |
| 1192 |
* Django 1.8 :commit:`(patch) <6118ab7d0676f0d622278e5be215f14fb5410b6a>` |
| 1193 |
|
| 1194 |
July 18, 2016 - :cve:`2016-6186` |
| 1195 |
-------------------------------- |
| 1196 |
|
| 1197 |
XSS in admin's add/change related popup. `Full description |
| 1198 |
<https://www.djangoproject.com/weblog/2016/jul/18/security-releases/>`__ |
| 1199 |
|
| 1200 |
Versions affected |
| 1201 |
~~~~~~~~~~~~~~~~~ |
| 1202 |
|
| 1203 |
* Django 1.9 :commit:`(patch) <d03bf6fe4e9bf5b07de62c1a271c4b41a7d3d158>` |
| 1204 |
* Django 1.8 :commit:`(patch) <f68e5a99164867ab0e071a936470958ed867479d>` |
| 1205 |
|
| 1206 |
March 1, 2016 - :cve:`2016-2513` |
| 1207 |
-------------------------------- |
| 1208 |
|
| 1209 |
User enumeration through timing difference on password hasher work factor |
| 1210 |
upgrade. `Full description |
| 1211 |
<https://www.djangoproject.com/weblog/2016/mar/01/security-releases/>`__ |
| 1212 |
|
| 1213 |
Versions affected |
| 1214 |
~~~~~~~~~~~~~~~~~ |
| 1215 |
|
| 1216 |
* Django 1.9 :commit:`(patch) <af7d09b0c5c6ab68e629fd9baf736f9dd203b18e>` |
| 1217 |
* Django 1.8 :commit:`(patch) <f4e6e02f7713a6924d16540be279909ff4091eb6>` |
| 1218 |
|
| 1219 |
March 1, 2016 - :cve:`2016-2512` |
| 1220 |
-------------------------------- |
| 1221 |
|
| 1222 |
Malicious redirect and possible XSS attack via user-supplied redirect URLs |
| 1223 |
containing basic auth. `Full description |
| 1224 |
<https://www.djangoproject.com/weblog/2016/mar/01/security-releases/>`__ |
| 1225 |
|
| 1226 |
Versions affected |
| 1227 |
~~~~~~~~~~~~~~~~~ |
| 1228 |
|
| 1229 |
* Django 1.9 :commit:`(patch) <fc6d147a63f89795dbcdecb0559256470fff4380>` |
| 1230 |
* Django 1.8 :commit:`(patch) <382ab137312961ad62feb8109d70a5a581fe8350>` |
| 1231 |
|
| 1232 |
February 1, 2016 - :cve:`2016-2048` |
| 1233 |
----------------------------------- |
| 1234 |
|
| 1235 |
User with "change" but not "add" permission can create objects for |
| 1236 |
``ModelAdmin``’s with ``save_as=True``. `Full description |
| 1237 |
<https://www.djangoproject.com/weblog/2016/feb/01/releases-192-and-189/>`__ |
| 1238 |
|
| 1239 |
Versions affected |
| 1240 |
~~~~~~~~~~~~~~~~~ |
| 1241 |
|
| 1242 |
* Django 1.9 :commit:`(patch) <adbca5e4db42542575734b8e5d26961c8ada7265>` |
| 1243 |
|
| 1244 |
November 24, 2015 - :cve:`2015-8213` |
| 1245 |
------------------------------------ |
| 1246 |
|
| 1247 |
Settings leak possibility in ``date`` template filter. `Full description |
| 1248 |
<https://www.djangoproject.com/weblog/2015/nov/24/security-releases-issued/>`__ |
| 1249 |
|
| 1250 |
Versions affected |
| 1251 |
~~~~~~~~~~~~~~~~~ |
| 1252 |
|
| 1253 |
* Django 1.8 :commit:`(patch) <9f83fc2f66f5a0bac7c291aec55df66050bb6991>` |
| 1254 |
* Django 1.7 :commit:`(patch) <8a01c6b53169ee079cb21ac5919fdafcc8c5e172>` |
| 1255 |
|
| 1256 |
August 18, 2015 - :cve:`2015-5963` / :cve:`2015-5964` |
| 1257 |
----------------------------------------------------- |
| 1258 |
|
| 1259 |
Denial-of-service possibility in ``logout()`` view by filling session store. |
| 1260 |
`Full description <https://www.djangoproject.com/weblog/2015/aug/18/security-releases/>`__ |
| 1261 |
|
| 1262 |
Versions affected |
| 1263 |
~~~~~~~~~~~~~~~~~ |
| 1264 |
|
| 1265 |
* Django 1.8 :commit:`(patch) <2eb86b01d7b59be06076f6179a454d0fd0afaff6>` |
| 1266 |
* Django 1.7 :commit:`(patch) <2f5485346ee6f84b4e52068c04e043092daf55f7>` |
| 1267 |
* Django 1.4 :commit:`(patch) <575f59f9bc7c59a5e41a081d1f5f55fc859c5012>` |
| 1268 |
|
| 1269 |
July 8, 2015 - :cve:`2015-5145` |
| 1270 |
------------------------------- |
| 1271 |
|
| 1272 |
Denial-of-service possibility in URL validation. `Full description |
| 1273 |
<https://www.djangoproject.com/weblog/2015/jul/08/security-releases/>`__ |
| 1274 |
|
| 1275 |
Versions affected |
| 1276 |
~~~~~~~~~~~~~~~~~ |
| 1277 |
|
| 1278 |
* Django 1.8 :commit:`(patch) <8f9a4d3a2bc42f14bb437defd30c7315adbff22c>` |
| 1279 |
|
| 1280 |
July 8, 2015 - :cve:`2015-5144` |
| 1281 |
------------------------------- |
| 1282 |
|
| 1283 |
Header injection possibility since validators accept newlines in input. `Full |
| 1284 |
description <https://www.djangoproject.com/weblog/2015/jul/08/security-releases/>`__ |
| 1285 |
|
| 1286 |
Versions affected |
| 1287 |
~~~~~~~~~~~~~~~~~ |
| 1288 |
|
| 1289 |
* Django 1.8 :commit:`(patch) <574dd5e0b0fbb877ae5827b1603d298edc9bb2a0>` |
| 1290 |
* Django 1.7 :commit:`(patch) <ae49b4d994656bc037513dcd064cb9ce5bb85649>` |
| 1291 |
* Django 1.4 :commit:`(patch) <1ba1cdce7d58e6740fe51955d945b56ae51d072a>` |
| 1292 |
|
| 1293 |
July 8, 2015 - :cve:`2015-5143` |
| 1294 |
------------------------------- |
| 1295 |
|
| 1296 |
Denial-of-service possibility by filling session store. `Full |
| 1297 |
description <https://www.djangoproject.com/weblog/2015/jul/08/security-releases/>`__ |
| 1298 |
|
| 1299 |
Versions affected |
| 1300 |
~~~~~~~~~~~~~~~~~ |
| 1301 |
|
| 1302 |
* Django 1.8 :commit:`(patch) <66d12d1ababa8f062857ee5eb43276493720bf16>` |
| 1303 |
* Django 1.7 :commit:`(patch) <1828f4341ec53a8684112d24031b767eba557663>` |
| 1304 |
* Django 1.4 :commit:`(patch) <2e47f3e401c29bc2ba5ab794d483cb0820855fb9>` |
| 1305 |
|
| 1306 |
May 20, 2015 - :cve:`2015-3982` |
| 1307 |
------------------------------- |
| 1308 |
|
| 1309 |
Fixed session flushing in the cached_db backend. `Full description |
| 1310 |
<https://www.djangoproject.com/weblog/2015/may/20/security-release/>`__ |
| 1311 |
|
| 1312 |
Versions affected |
| 1313 |
~~~~~~~~~~~~~~~~~ |
| 1314 |
|
| 1315 |
* Django 1.8 :commit:`(patch) <31cb25adecba930bdeee4556709f5a1c42d88fd6>` |
| 1316 |
|
| 1317 |
March 18, 2015 - :cve:`2015-2317` |
| 1318 |
--------------------------------- |
| 1319 |
|
| 1320 |
Mitigated possible XSS attack via user-supplied redirect URLs. `Full |
| 1321 |
description <https://www.djangoproject.com/weblog/2015/mar/18/security-releases/>`__ |
| 1322 |
|
| 1323 |
Versions affected |
| 1324 |
~~~~~~~~~~~~~~~~~ |
| 1325 |
|
| 1326 |
* Django 1.4 :commit:`(patch) <2342693b31f740a422abf7267c53b4e7bc487c1b>` |
| 1327 |
* Django 1.6 :commit:`(patch) <5510f070711540aaa8d3707776cd77494e688ef9>` |
| 1328 |
* Django 1.7 :commit:`(patch) <2a4113dbd532ce952308992633d802dc169a75f1>` |
| 1329 |
* Django 1.8 :commit:`(patch) <770427c2896a078925abfca2317486b284d22f04>` |
| 1330 |
|
| 1331 |
March 18, 2015 - :cve:`2015-2316` |
| 1332 |
--------------------------------- |
| 1333 |
|
| 1334 |
Denial-of-service possibility with ``strip_tags()``. `Full description |
| 1335 |
<https://www.djangoproject.com/weblog/2015/mar/18/security-releases/>`__ |
| 1336 |
|
| 1337 |
Versions affected |
| 1338 |
~~~~~~~~~~~~~~~~~ |
| 1339 |
|
| 1340 |
* Django 1.6 :commit:`(patch) <b6b3cb9899214a23ebb0f4ebf0e0b300b0ee524f>` |
| 1341 |
* Django 1.7 :commit:`(patch) <e63363f8e075fa8d66326ad6a1cc3391cc95cd97>` |
| 1342 |
* Django 1.8 :commit:`(patch) <5447709a571cd5d95971f1d5d21d4a7edcf85bbd>` |
| 1343 |
|
| 1344 |
March 9, 2015 - :cve:`2015-2241` |
| 1345 |
-------------------------------- |
| 1346 |
|
| 1347 |
XSS attack via properties in ``ModelAdmin.readonly_fields``. `Full description |
| 1348 |
<https://www.djangoproject.com/weblog/2015/mar/09/security-releases/>`__ |
| 1349 |
|
| 1350 |
Versions affected |
| 1351 |
~~~~~~~~~~~~~~~~~ |
| 1352 |
|
| 1353 |
* Django 1.7 :commit:`(patch) <d16e4e1d6f95e6f46bff53cc4fd0ab398b8e5059>` |
| 1354 |
* Django 1.8 :commit:`(patch) <2654e1b93923bac55f12b4e66c5e39b16695ace5>` |
| 1355 |
|
| 1356 |
January 13, 2015 - :cve:`2015-0222` |
| 1357 |
----------------------------------- |
| 1358 |
|
| 1359 |
Database denial-of-service with ``ModelMultipleChoiceField``. `Full description |
| 1360 |
<https://www.djangoproject.com/weblog/2015/jan/13/security/>`__ |
| 1361 |
|
| 1362 |
Versions affected |
| 1363 |
~~~~~~~~~~~~~~~~~ |
| 1364 |
|
| 1365 |
* Django 1.6 :commit:`(patch) <d7a06ee7e571b6dad07c0f5b519b1db02e2a476c>` |
| 1366 |
* Django 1.7 :commit:`(patch) <bcfb47780ce7caecb409a9e9c1c314266e41d392>` |
| 1367 |
|
| 1368 |
January 13, 2015 - :cve:`2015-0221` |
| 1369 |
----------------------------------- |
| 1370 |
|
| 1371 |
Denial-of-service attack against ``django.views.static.serve()``. `Full |
| 1372 |
description <https://www.djangoproject.com/weblog/2015/jan/13/security/>`__ |
| 1373 |
|
| 1374 |
Versions affected |
| 1375 |
~~~~~~~~~~~~~~~~~ |
| 1376 |
|
| 1377 |
* Django 1.4 :commit:`(patch) <d020da6646c5142bc092247d218a3d1ce3e993f7>` |
| 1378 |
* Django 1.6 :commit:`(patch) <553779c4055e8742cc832ed525b9ee34b174934f>` |
| 1379 |
* Django 1.7 :commit:`(patch) <818e59a3f0fbadf6c447754d202d88df025f8f2a>` |
| 1380 |
|
| 1381 |
January 13, 2015 - :cve:`2015-0220` |
| 1382 |
----------------------------------- |
| 1383 |
|
| 1384 |
Mitigated possible XSS attack via user-supplied redirect URLs. `Full |
| 1385 |
description <https://www.djangoproject.com/weblog/2015/jan/13/security/>`__ |
| 1386 |
|
| 1387 |
Versions affected |
| 1388 |
~~~~~~~~~~~~~~~~~ |
| 1389 |
|
| 1390 |
* Django 1.4 :commit:`(patch) <4c241f1b710da6419d9dca160e80b23b82db7758>` |
| 1391 |
* Django 1.6 :commit:`(patch) <72e0b033662faa11bb7f516f18a132728aa0ae28>` |
| 1392 |
* Django 1.7 :commit:`(patch) <de67dedc771ad2edec15c1d00c083a1a084e1e89>` |
| 1393 |
|
| 1394 |
January 13, 2015 - :cve:`2015-0219` |
| 1395 |
----------------------------------- |
| 1396 |
|
| 1397 |
WSGI header spoofing via underscore/dash conflation. `Full description |
| 1398 |
<https://www.djangoproject.com/weblog/2015/jan/13/security/>`__ |
| 1399 |
|
| 1400 |
Versions affected |
| 1401 |
~~~~~~~~~~~~~~~~~ |
| 1402 |
|
| 1403 |
* Django 1.4 :commit:`(patch) <4f6fffc1dc429f1ad428ecf8e6620739e8837450>` |
| 1404 |
* Django 1.6 :commit:`(patch) <d7597b31d5c03106eeba4be14a33b32a5e25f4ee>` |
| 1405 |
* Django 1.7 :commit:`(patch) <41b4bc73ee0da7b2e09f4af47fc1fd21144c710f>` |
| 1406 |
|
| 1407 |
August 20, 2014 - :cve:`2014-0483` |
| 1408 |
---------------------------------- |
| 1409 |
|
| 1410 |
Data leakage via querystring manipulation in admin. |
| 1411 |
`Full description <https://www.djangoproject.com/weblog/2014/aug/20/security/>`__ |
| 1412 |
|
| 1413 |
Versions affected |
| 1414 |
~~~~~~~~~~~~~~~~~ |
| 1415 |
|
| 1416 |
* Django 1.4 :commit:`(patch) <027bd348642007617518379f8b02546abacaa6e0>` |
| 1417 |
* Django 1.5 :commit:`(patch) <2a446c896e7c814661fb9c4f212b071b2a7fa446>` |
| 1418 |
* Django 1.6 :commit:`(patch) <f7c494f2506250b8cb5923714360a3642ed63e0f>` |
| 1419 |
* Django 1.7 :commit:`(patch) <2b31342cdf14fc20e07c43d258f1e7334ad664a6>` |
| 1420 |
|
| 1421 |
August 20, 2014 - :cve:`2014-0482` |
| 1422 |
---------------------------------- |
| 1423 |
|
| 1424 |
``RemoteUserMiddleware`` session hijacking. `Full description |
| 1425 |
<https://www.djangoproject.com/weblog/2014/aug/20/security/>`__ |
| 1426 |
|
| 1427 |
Versions affected |
| 1428 |
~~~~~~~~~~~~~~~~~ |
| 1429 |
|
| 1430 |
* Django 1.4 :commit:`(patch) <c9e3b9949cd55f090591fbdc4a114fcb8368b6d9>` |
| 1431 |
* Django 1.5 :commit:`(patch) <dd68f319b365f6cb38c5a6c106faf4f6142d7d88>` |
| 1432 |
* Django 1.6 :commit:`(patch) <0268b855f9eab3377f2821164ef3e66037789e09>` |
| 1433 |
* Django 1.7 :commit:`(patch) <1a45d059c70385fcd6f4a3955f3b4e4cc96d0150>` |
| 1434 |
|
| 1435 |
August 20, 2014 - :cve:`2014-0481` |
| 1436 |
---------------------------------- |
| 1437 |
|
| 1438 |
File upload denial of service. `Full description |
| 1439 |
<https://www.djangoproject.com/weblog/2014/aug/20/security/>`__ |
| 1440 |
|
| 1441 |
Versions affected |
| 1442 |
~~~~~~~~~~~~~~~~~ |
| 1443 |
|
| 1444 |
* Django 1.4 :commit:`(patch) <30042d475bf084c6723c6217a21598d9247a9c41>` |
| 1445 |
* Django 1.5 :commit:`(patch) <26cd48e166ac4d84317c8ee6d63ac52a87e8da99>` |
| 1446 |
* Django 1.6 :commit:`(patch) <dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1>` |
| 1447 |
* Django 1.7 :commit:`(patch) <3123f8452cf49071be9110e277eea60ba0032216>` |
| 1448 |
|
| 1449 |
August 20, 2014 - :cve:`2014-0480` |
| 1450 |
---------------------------------- |
| 1451 |
|
| 1452 |
``reverse()`` can generate URLs pointing to other hosts. `Full description |
| 1453 |
<https://www.djangoproject.com/weblog/2014/aug/20/security/>`__ |
| 1454 |
|
| 1455 |
Versions affected |
| 1456 |
~~~~~~~~~~~~~~~~~ |
| 1457 |
|
| 1458 |
* Django 1.4 :commit:`(patch) <c2fe73133b62a1d9e8f7a6b43966570b14618d7e>` |
| 1459 |
* Django 1.5 :commit:`(patch) <45ac9d4fb087d21902469fc22643f5201d41a0cd>` |
| 1460 |
* Django 1.6 :commit:`(patch) <da051da8df5e69944745072611351d4cfc6435d5>` |
| 1461 |
* Django 1.7 :commit:`(patch) <bf650a2ee78c6d1f4544a875dcc777cf27fe93e9>` |
| 1462 |
|
| 1463 |
May 18, 2014 - :cve:`2014-3730` |
| 1464 |
------------------------------- |
| 1465 |
|
| 1466 |
Malformed URLs from user input incorrectly validated. `Full description |
| 1467 |
<https://www.djangoproject.com/weblog/2014/may/14/security-releases-issued/>`__ |
| 1468 |
|
| 1469 |
Versions affected |
| 1470 |
~~~~~~~~~~~~~~~~~ |
| 1471 |
|
| 1472 |
* Django 1.4 :commit:`(patch) <7feb54bbae3f637ab3c4dd4831d4385964f574df>` |
| 1473 |
* Django 1.5 :commit:`(patch) <ad32c218850ad40972dcef57beb460f8c979dd6d>` |
| 1474 |
* Django 1.6 :commit:`(patch) <601107524523bca02376a0ddc1a06c6fdb8f22f3>` |
| 1475 |
* Django 1.7 :commit:`(patch) <e7b0cace455c2da24492660636bfd48c45a19cdf>` |
| 1476 |
|
| 1477 |
May 18, 2014 - :cve:`2014-1418` |
| 1478 |
------------------------------- |
| 1479 |
|
| 1480 |
Caches may be allowed to store and serve private data. `Full description |
| 1481 |
<https://www.djangoproject.com/weblog/2014/may/14/security-releases-issued/>`__ |
| 1482 |
|
| 1483 |
Versions affected |
| 1484 |
~~~~~~~~~~~~~~~~~ |
| 1485 |
|
| 1486 |
* Django 1.4 :commit:`(patch) <28e23306aa53bbbb8fb87db85f99d970b051026c>` |
| 1487 |
* Django 1.5 :commit:`(patch) <4001ec8698f577b973c5a540801d8a0bbea1205b>` |
| 1488 |
* Django 1.6 :commit:`(patch) <1abcf3a808b35abae5d425ed4d44cb6e886dc769>` |
| 1489 |
* Django 1.7 :commit:`(patch) <7fef18ba9e5a8b47bc24b5bb259c8bf3d3879f2a>` |
| 1490 |
|
| 1491 |
April 21, 2014 - :cve:`2014-0474` |
| 1492 |
--------------------------------- |
| 1493 |
|
| 1494 |
MySQL typecasting causes unexpected query results. `Full description |
| 1495 |
<https://www.djangoproject.com/weblog/2014/apr/21/security/>`__ |
| 1496 |
|
| 1497 |
Versions affected |
| 1498 |
~~~~~~~~~~~~~~~~~ |
| 1499 |
|
| 1500 |
* Django 1.4 :commit:`(patch) <aa80f498de6d687e613860933ac58433ab71ea4b>` |
| 1501 |
* Django 1.5 :commit:`(patch) <985434fb1d6bf2335bf96c6ebf91c3674f1f399f>` |
| 1502 |
* Django 1.6 :commit:`(patch) <5f0829a27e85d89ad8c433f5c6a7a7d17c9e9292>` |
| 1503 |
* Django 1.7 :commit:`(patch) <34526c2f56b863c2103655a0893ac801667e86ea>` |
| 1504 |
|
| 1505 |
April 21, 2014 - :cve:`2014-0473` |
| 1506 |
--------------------------------- |
| 1507 |
|
| 1508 |
Caching of anonymous pages could reveal CSRF token. `Full description |
| 1509 |
<https://www.djangoproject.com/weblog/2014/apr/21/security/>`__ |
| 1510 |
|
| 1511 |
Versions affected |
| 1512 |
~~~~~~~~~~~~~~~~~ |
| 1513 |
|
| 1514 |
* Django 1.4 :commit:`(patch) <1170f285ddd6a94a65f911a27788ba49ca08c0b0>` |
| 1515 |
* Django 1.5 :commit:`(patch) <6872f42757d7ef6a97e0b6ec5db4d2615d8a2bd8>` |
| 1516 |
* Django 1.6 :commit:`(patch) <d63e20942f3024f24cb8cd85a49461ba8a9b6736>` |
| 1517 |
* Django 1.7 :commit:`(patch) <380545bf85cbf17fc698d136815b7691f8d023ca>` |
| 1518 |
|
| 1519 |
April 21, 2014 - :cve:`2014-0472` |
| 1520 |
--------------------------------- |
| 1521 |
|
| 1522 |
Unexpected code execution using ``reverse()``. `Full description |
| 1523 |
<https://www.djangoproject.com/weblog/2014/apr/21/security/>`__ |
| 1524 |
|
| 1525 |
Versions affected |
| 1526 |
~~~~~~~~~~~~~~~~~ |
| 1527 |
|
| 1528 |
* Django 1.4 :commit:`(patch) <c1a8c420fe4b27fb2caf5e46d23b5712fc0ac535>` |
| 1529 |
* Django 1.5 :commit:`(patch) <2a5bcb69f42b84464b24b5c835dca6467b6aa7f1>` |
| 1530 |
* Django 1.6 :commit:`(patch) <4352a50871e239ebcdf64eee6f0b88e714015c1b>` |
| 1531 |
* Django 1.7 :commit:`(patch) <546740544d7f69254a67b06a3fc7fa0c43512958>` |
| 1532 |
|
| 1533 |
September 14, 2013 - :cve:`2013-1443` |
| 1534 |
------------------------------------- |
| 1535 |
|
| 1536 |
Denial-of-service via large passwords. `Full description |
| 1537 |
<https://www.djangoproject.com/weblog/2013/sep/15/security/>`__ |
| 1538 |
|
| 1539 |
Versions affected |
| 1540 |
~~~~~~~~~~~~~~~~~ |
| 1541 |
|
| 1542 |
* Django 1.4 :commit:`(patch <3f3d887a6844ec2db743fee64c9e53e04d39a368>` and :commit:`Python compatibility fix) <6903d1690a92aa040adfb0c8eb37cf62e4206714>` |
| 1543 |
* Django 1.5 :commit:`(patch) <22b74fa09d7ccbc8c52270d648a0da7f3f0fa2bc>` |
| 1544 |
|
| 1545 |
September 10, 2013 - :cve:`2013-4315` |
| 1546 |
------------------------------------- |
| 1547 |
|
| 1548 |
Directory-traversal via ``ssi`` template tag. `Full description |
| 1549 |
<https://www.djangoproject.com/weblog/2013/sep/10/security-releases-issued/>`__ |
| 1550 |
|
| 1551 |
Versions affected |
| 1552 |
~~~~~~~~~~~~~~~~~ |
| 1553 |
|
| 1554 |
* Django 1.4 :commit:`(patch) <87d2750b39f6f2d54b7047225521a44dcd37e896>` |
| 1555 |
* Django 1.5 :commit:`(patch) <988b61c550d798f9a66d17ee0511fb7a9a7f33ca>` |
| 1556 |
|
| 1557 |
August 13, 2013 - :cve:`2013-6044` |
| 1558 |
---------------------------------- |
| 1559 |
|
| 1560 |
Possible XSS via unvalidated URL redirect schemes. `Full description |
| 1561 |
<https://www.djangoproject.com/weblog/2013/aug/13/security-releases-issued/>`__ |
| 1562 |
|
| 1563 |
Versions affected |
| 1564 |
~~~~~~~~~~~~~~~~~ |
| 1565 |
|
| 1566 |
* Django 1.4 :commit:`(patch) <ec67af0bd609c412b76eaa4cc89968a2a8e5ad6a>` |
| 1567 |
* Django 1.5 :commit:`(patch) <1a274ccd6bc1afbdac80344c9b6e5810c1162b5f>` |
| 1568 |
|
| 1569 |
August 13, 2013 - :cve:`2013-4249` |
| 1570 |
---------------------------------- |
| 1571 |
|
| 1572 |
XSS via admin trusting ``URLField`` values. `Full description |
| 1573 |
<https://www.djangoproject.com/weblog/2013/aug/13/security-releases-issued/>`__ |
| 1574 |
|
| 1575 |
Versions affected |
| 1576 |
~~~~~~~~~~~~~~~~~ |
| 1577 |
|
| 1578 |
* Django 1.5 :commit:`(patch) <90363e388c61874add3f3557ee654a996ec75d78>` |
| 1579 |
|
| 1580 |
February 19, 2013 - :cve:`2013-0306` |
| 1581 |
------------------------------------ |
| 1582 |
|
| 1583 |
Denial-of-service via formset ``max_num`` bypass. `Full description |
| 1584 |
<https://www.djangoproject.com/weblog/2013/feb/19/security/>`__ |
| 1585 |
|
| 1586 |
Versions affected |
| 1587 |
~~~~~~~~~~~~~~~~~ |
| 1588 |
|
| 1589 |
* Django 1.3 :commit:`(patch) <d7094bbce8cb838f3b40f504f198c098ff1cf727>` |
| 1590 |
* Django 1.4 :commit:`(patch) <0cc350a896f70ace18280410eb616a9197d862b0>` |
| 1591 |
|
| 1592 |
February 19, 2013 - :cve:`2013-0305` |
| 1593 |
------------------------------------ |
| 1594 |
|
| 1595 |
Information leakage via admin history log. `Full description |
| 1596 |
<https://www.djangoproject.com/weblog/2013/feb/19/security/>`__ |
| 1597 |
|
| 1598 |
Versions affected |
| 1599 |
~~~~~~~~~~~~~~~~~ |
| 1600 |
|
| 1601 |
* Django 1.3 :commit:`(patch) <d3a45e10c8ac8268899999129daa27652ec0da35>` |
| 1602 |
* Django 1.4 :commit:`(patch) <0e7861aec73702f7933ce2a93056f7983939f0d6>` |
| 1603 |
|
| 1604 |
February 19, 2013 - :cve:`2013-1664` / :cve:`2013-1665` |
| 1605 |
------------------------------------------------------- |
| 1606 |
|
| 1607 |
Entity-based attacks against Python XML libraries. `Full description |
| 1608 |
<https://www.djangoproject.com/weblog/2013/feb/19/security/>`__ |
| 1609 |
|
| 1610 |
Versions affected |
| 1611 |
~~~~~~~~~~~~~~~~~ |
| 1612 |
|
| 1613 |
* Django 1.3 :commit:`(patch) <d19a27066b2247102e65412aa66917aff0091112>` |
| 1614 |
* Django 1.4 :commit:`(patch) <1c60d07ba23e0350351c278ad28d0bd5aa410b40>` |
| 1615 |
|
| 1616 |
February 19, 2013 - No CVE |
| 1617 |
-------------------------- |
| 1618 |
|
| 1619 |
Additional hardening of ``Host`` header handling. `Full description |
| 1620 |
<https://www.djangoproject.com/weblog/2013/feb/19/security/>`__ |
| 1621 |
|
| 1622 |
Versions affected |
| 1623 |
~~~~~~~~~~~~~~~~~ |
| 1624 |
|
| 1625 |
* Django 1.3 :commit:`(patch) <27cd872e6e36a81d0bb6f5b8765a1705fecfc253>` |
| 1626 |
* Django 1.4 :commit:`(patch) <9936fdb11d0bbf0bd242f259bfb97bbf849d16f8>` |
| 1627 |
|
| 1628 |
December 10, 2012 - No CVE 2 |
| 1629 |
---------------------------- |
| 1630 |
|
| 1631 |
Additional hardening of redirect validation. `Full description |
| 1632 |
<https://www.djangoproject.com/weblog/2012/dec/10/security/>`__ |
| 1633 |
|
| 1634 |
Versions affected |
| 1635 |
~~~~~~~~~~~~~~~~~ |
| 1636 |
|
| 1637 |
* Django 1.3: :commit:`(patch) <1515eb46daa0897ba5ad5f0a2db8969255f1b343>` |
| 1638 |
* Django 1.4: :commit:`(patch) <b2ae0a63aeec741f1e51bac9a95a27fd635f9652>` |
| 1639 |
|
| 1640 |
December 10, 2012 - No CVE 1 |
| 1641 |
---------------------------- |
| 1642 |
|
| 1643 |
Additional hardening of ``Host`` header handling. `Full description |
| 1644 |
<https://www.djangoproject.com/weblog/2012/dec/10/security/>`__ |
| 1645 |
|
| 1646 |
Versions affected |
| 1647 |
~~~~~~~~~~~~~~~~~ |
| 1648 |
|
| 1649 |
* Django 1.3 :commit:`(patch) <2da4ace0bc1bc1d79bf43b368cb857f6f0cd6b1b>` |
| 1650 |
* Django 1.4 :commit:`(patch) <319627c184e71ae267d6b7f000e293168c7b6e09>` |
| 1651 |
|
| 1652 |
October 17, 2012 - :cve:`2012-4520` |
| 1653 |
----------------------------------- |
| 1654 |
|
| 1655 |
``Host`` header poisoning. `Full description |
| 1656 |
<https://www.djangoproject.com/weblog/2012/oct/17/security/>`__ |
| 1657 |
|
| 1658 |
Versions affected |
| 1659 |
~~~~~~~~~~~~~~~~~ |
| 1660 |
|
| 1661 |
* Django 1.3 :commit:`(patch) <b45c377f8f488955e0c7069cad3f3dd21910b071>` |
| 1662 |
* Django 1.4 :commit:`(patch) <92d3430f12171f16f566c9050c40feefb830a4a3>` |
| 1663 |
|
| 1664 |
July 30, 2012 - :cve:`2012-3444` |
| 1665 |
-------------------------------- |
| 1666 |
|
| 1667 |
Denial-of-service via large image files. `Full description |
| 1668 |
<https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/>`__ |
| 1669 |
|
| 1670 |
Versions affected |
| 1671 |
~~~~~~~~~~~~~~~~~ |
| 1672 |
|
| 1673 |
* Django 1.3 :commit:`(patch) <9ca0ff6268eeff92d0d0ac2c315d4b6a8e229155>` |
| 1674 |
* Django 1.4 :commit:`(patch) <da33d67181b53fe6cc737ac1220153814a1509f6>` |
| 1675 |
|
| 1676 |
July 30, 2012 - :cve:`2012-3443` |
| 1677 |
-------------------------------- |
| 1678 |
|
| 1679 |
Denial-of-service via compressed image files. `Full description |
| 1680 |
<https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/>`__ |
| 1681 |
|
| 1682 |
Versions affected |
| 1683 |
~~~~~~~~~~~~~~~~~ |
| 1684 |
|
| 1685 |
* Django 1.3: :commit:`(patch) <b2eb4787a0fff9c9993b78be5c698e85108f3446>` |
| 1686 |
* Django 1.4: :commit:`(patch) <c14f325c4eef628bc7bfd8873c3a72aeb0219141>` |
| 1687 |
|
| 1688 |
July 30, 2012 - :cve:`2012-3442` |
| 1689 |
-------------------------------- |
| 1690 |
|
| 1691 |
XSS via failure to validate redirect scheme. `Full description |
| 1692 |
<https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/>`__ |
| 1693 |
|
| 1694 |
Versions affected |
| 1695 |
~~~~~~~~~~~~~~~~~ |
| 1696 |
|
| 1697 |
* Django 1.3: :commit:`(patch) <4dea4883e6c50d75f215a6b9bcbd95273f57c72d>` |
| 1698 |
* Django 1.4: :commit:`(patch) <e34685034b60be1112160e76091e5aee60149fa1>` |
| 1699 |
|
| 1700 |
September 9, 2011 - :cve:`2011-4140` |
| 1701 |
------------------------------------ |
| 1702 |
|
| 1703 |
Potential CSRF via ``Host`` header. `Full description |
| 1704 |
<https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__ |
| 1705 |
|
| 1706 |
Versions affected |
| 1707 |
~~~~~~~~~~~~~~~~~ |
| 1708 |
|
| 1709 |
This notification was an advisory only, so no patches were issued. |
| 1710 |
|
| 1711 |
* Django 1.2 |
| 1712 |
* Django 1.3 |
| 1713 |
|
| 1714 |
September 9, 2011 - :cve:`2011-4139` |
| 1715 |
------------------------------------ |
| 1716 |
|
| 1717 |
``Host`` header cache poisoning. `Full description |
| 1718 |
<https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__ |
| 1719 |
|
| 1720 |
Versions affected |
| 1721 |
~~~~~~~~~~~~~~~~~ |
| 1722 |
|
| 1723 |
* Django 1.2 :commit:`(patch) <c613af4d6485586c79d692b70a9acac429f3ca9d>` |
| 1724 |
* Django 1.3 :commit:`(patch) <2f7fadc38efa58ac0a8f93f936b82332a199f396>` |
| 1725 |
|
| 1726 |
September 9, 2011 - :cve:`2011-4138` |
| 1727 |
------------------------------------ |
| 1728 |
|
| 1729 |
Information leakage/arbitrary request issuance via ``URLField.verify_exists``. |
| 1730 |
`Full description |
| 1731 |
<https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__ |
| 1732 |
|
| 1733 |
Versions affected |
| 1734 |
~~~~~~~~~~~~~~~~~ |
| 1735 |
|
| 1736 |
* Django 1.2: :commit:`(patch) <7268f8af86186518821d775c530d5558fd726930>` |
| 1737 |
* Django 1.3: :commit:`(patch) <1a76dbefdfc60e2d5954c0ba614c3d054ba9c3f0>` |
| 1738 |
|
| 1739 |
September 9, 2011 - :cve:`2011-4137` |
| 1740 |
------------------------------------ |
| 1741 |
|
| 1742 |
Denial-of-service via ``URLField.verify_exists``. `Full description |
| 1743 |
<https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__ |
| 1744 |
|
| 1745 |
Versions affected |
| 1746 |
~~~~~~~~~~~~~~~~~ |
| 1747 |
|
| 1748 |
* Django 1.2 :commit:`(patch) <7268f8af86186518821d775c530d5558fd726930>` |
| 1749 |
* Django 1.3 :commit:`(patch) <1a76dbefdfc60e2d5954c0ba614c3d054ba9c3f0>` |
| 1750 |
|
| 1751 |
September 9, 2011 - :cve:`2011-4136` |
| 1752 |
------------------------------------ |
| 1753 |
|
| 1754 |
Session manipulation when using memory-cache-backed session. `Full description |
| 1755 |
<https://www.djangoproject.com/weblog/2011/sep/09/security-releases-issued/>`__ |
| 1756 |
|
| 1757 |
Versions affected |
| 1758 |
~~~~~~~~~~~~~~~~~ |
| 1759 |
|
| 1760 |
* Django 1.2 :commit:`(patch) <ac7c3a110f906e4dfed3a17451bf7fd9fcb81296>` |
| 1761 |
* Django 1.3 :commit:`(patch) <fbe2eead2fa9d808658ca582241bcacb02618840>` |
| 1762 |
|
| 1763 |
February 8, 2011 - :cve:`2011-0698` |
| 1764 |
----------------------------------- |
| 1765 |
|
| 1766 |
Directory-traversal on Windows via incorrect path-separator handling. `Full |
| 1767 |
description <https://www.djangoproject.com/weblog/2011/feb/08/security/>`__ |
| 1768 |
|
| 1769 |
Versions affected |
| 1770 |
~~~~~~~~~~~~~~~~~ |
| 1771 |
|
| 1772 |
* Django 1.1 :commit:`(patch) <570a32a047ea56265646217264b0d3dab1a14dbd>` |
| 1773 |
* Django 1.2 :commit:`(patch) <194566480b15cf4e294d3f03ff587019b74044b2>` |
| 1774 |
|
| 1775 |
February 8, 2011 - :cve:`2011-0697` |
| 1776 |
----------------------------------- |
| 1777 |
|
| 1778 |
XSS via unsanitized names of uploaded files. `Full description |
| 1779 |
<https://www.djangoproject.com/weblog/2011/feb/08/security/>`__ |
| 1780 |
|
| 1781 |
Versions affected |
| 1782 |
~~~~~~~~~~~~~~~~~ |
| 1783 |
|
| 1784 |
* Django 1.1 :commit:`(patch) <1966786d2dde73e17f39cf340eb33fcb5d73904e>` |
| 1785 |
* Django 1.2 :commit:`(patch) <1f814a9547842dcfabdae09573055984af9d3fab>` |
| 1786 |
|
| 1787 |
February 8, 2011 - :cve:`2011-0696` |
| 1788 |
----------------------------------- |
| 1789 |
|
| 1790 |
CSRF via forged HTTP headers. `Full description |
| 1791 |
<https://www.djangoproject.com/weblog/2011/feb/08/security/>`__ |
| 1792 |
|
| 1793 |
Versions affected |
| 1794 |
~~~~~~~~~~~~~~~~~ |
| 1795 |
|
| 1796 |
* Django 1.1 :commit:`(patch) <408c5c873ce1437c7eee9544ff279ecbad7e150a>` |
| 1797 |
* Django 1.2 :commit:`(patch) <818e70344e7193f6ebc73c82ed574e6ce3c91afc>` |
| 1798 |
|
| 1799 |
December 22, 2010 - :cve:`2010-4535` |
| 1800 |
------------------------------------ |
| 1801 |
|
| 1802 |
Denial-of-service in password-reset mechanism. `Full description |
| 1803 |
<https://www.djangoproject.com/weblog/2010/dec/22/security/>`__ |
| 1804 |
|
| 1805 |
Versions affected |
| 1806 |
~~~~~~~~~~~~~~~~~ |
| 1807 |
|
| 1808 |
* Django 1.1 :commit:`(patch) <7f8dd9cbac074389af8d8fd235bf2cb657227b9a>` |
| 1809 |
* Django 1.2 :commit:`(patch) <d5d8942a160685c403d381a279e72e09de5489a9>` |
| 1810 |
|
| 1811 |
December 22, 2010 - :cve:`2010-4534` |
| 1812 |
------------------------------------ |
| 1813 |
|
| 1814 |
Information leakage in administrative interface. `Full description |
| 1815 |
<https://www.djangoproject.com/weblog/2010/dec/22/security/>`__ |
| 1816 |
|
| 1817 |
Versions affected |
| 1818 |
~~~~~~~~~~~~~~~~~ |
| 1819 |
|
| 1820 |
* Django 1.1 :commit:`(patch) <17084839fd7e267da5729f2a27753322b9d415a0>` |
| 1821 |
* Django 1.2 :commit:`(patch) <85207a245bf09fdebe486b4c7bbcb65300f2a693>` |
| 1822 |
|
| 1823 |
September 8, 2010 - :cve:`2010-3082` |
| 1824 |
------------------------------------ |
| 1825 |
|
| 1826 |
XSS via trusting unsafe cookie value. `Full description |
| 1827 |
<https://www.djangoproject.com/weblog/2010/sep/08/security-release/>`__ |
| 1828 |
|
| 1829 |
Versions affected |
| 1830 |
~~~~~~~~~~~~~~~~~ |
| 1831 |
|
| 1832 |
* Django 1.2 :commit:`(patch) <7f84657b6b2243cc787bdb9f296710c8d13ad0bd>` |
| 1833 |
|
| 1834 |
October 9, 2009 - :cve:`2009-3695` |
| 1835 |
---------------------------------- |
| 1836 |
|
| 1837 |
Denial-of-service via pathological regular expression performance. `Full |
| 1838 |
description <https://www.djangoproject.com/weblog/2009/oct/09/security/>`__ |
| 1839 |
|
| 1840 |
Versions affected |
| 1841 |
~~~~~~~~~~~~~~~~~ |
| 1842 |
|
| 1843 |
* Django 1.0 :commit:`(patch) <594a28a9044120bed58671dde8a805c9e0f6c79a>` |
| 1844 |
* Django 1.1 :commit:`(patch) <e3e992e18b368fcd56aabafc1b5bf80a6e11b495>` |
| 1845 |
|
| 1846 |
July 28, 2009 - :cve:`2009-2659` |
| 1847 |
-------------------------------- |
| 1848 |
|
| 1849 |
Directory-traversal in development server media handler. `Full description |
| 1850 |
<https://www.djangoproject.com/weblog/2009/jul/28/security/>`__ |
| 1851 |
|
| 1852 |
Versions affected |
| 1853 |
~~~~~~~~~~~~~~~~~ |
| 1854 |
|
| 1855 |
* Django 0.96 :commit:`(patch) <da85d76fd6ca846f3b0ff414e042ddb5e62e2e69>` |
| 1856 |
* Django 1.0 :commit:`(patch) <df7f917b7f51ba969faa49d000ffc79572c5dcb4>` |
| 1857 |
|
| 1858 |
September 2, 2008 - :cve:`2008-3909` |
| 1859 |
------------------------------------ |
| 1860 |
|
| 1861 |
CSRF via preservation of POST data during admin login. `Full description |
| 1862 |
<https://www.djangoproject.com/weblog/2008/sep/02/security/>`__ |
| 1863 |
|
| 1864 |
Versions affected |
| 1865 |
~~~~~~~~~~~~~~~~~ |
| 1866 |
|
| 1867 |
* Django 0.91 :commit:`(patch) <44debfeaa4473bd28872c735dd3d9afde6886752>` |
| 1868 |
* Django 0.95 :commit:`(patch) <aee48854a164382c655acb9f18b3c06c3d238e81>` |
| 1869 |
* Django 0.96 :commit:`(patch) <7e0972bded362bc4b851c109df2c8a6548481a8e>` |
| 1870 |
|
| 1871 |
May 14, 2008 - :cve:`2008-2302` |
| 1872 |
------------------------------- |
| 1873 |
|
| 1874 |
XSS via admin login redirect. `Full description |
| 1875 |
<https://www.djangoproject.com/weblog/2008/may/14/security/>`__ |
| 1876 |
|
| 1877 |
Versions affected |
| 1878 |
~~~~~~~~~~~~~~~~~ |
| 1879 |
|
| 1880 |
* Django 0.91 :commit:`(patch) <6e657e2c404a96e744748209e896d8a69c15fdf2>` |
| 1881 |
* Django 0.95 :commit:`(patch) <50ce7fb57d79e8940ccf6e2781f2f01df029b5c5>` |
| 1882 |
* Django 0.96 :commit:`(patch) <7791e5c050cebf86d868c5dab7092185b125fdc9>` |
| 1883 |
|
| 1884 |
October 26, 2007 - :cve:`2007-5712` |
| 1885 |
----------------------------------- |
| 1886 |
|
| 1887 |
Denial-of-service via arbitrarily-large ``Accept-Language`` header. `Full |
| 1888 |
description <https://www.djangoproject.com/weblog/2007/oct/26/security-fix/>`__ |
| 1889 |
|
| 1890 |
Versions affected |
| 1891 |
~~~~~~~~~~~~~~~~~ |
| 1892 |
|
| 1893 |
* Django 0.91 :commit:`(patch) <8bc36e726c9e8c75c681d3ad232df8e882aaac81>` |
| 1894 |
* Django 0.95 :commit:`(patch) <412ed22502e11c50dbfee854627594f0e7e2c234>` |
| 1895 |
* Django 0.96 :commit:`(patch) <7dd2dd08a79e388732ce00e2b5514f15bd6d0f6f>` |
| 1896 |
|
| 1897 |
Issues prior to Django's security process |
| 1898 |
========================================= |
| 1899 |
|
| 1900 |
Some security issues were handled before Django had a formalized |
| 1901 |
security process in use. For these, new releases may not have been |
| 1902 |
issued at the time and CVEs may not have been assigned. |
| 1903 |
|
| 1904 |
January 21, 2007 - :cve:`2007-0405` |
| 1905 |
----------------------------------- |
| 1906 |
|
| 1907 |
Apparent "caching" of authenticated user. `Full description |
| 1908 |
<https://www.djangoproject.com/weblog/2007/jan/21/0951/>`__ |
| 1909 |
|
| 1910 |
Versions affected |
| 1911 |
~~~~~~~~~~~~~~~~~ |
| 1912 |
|
| 1913 |
* Django 0.95 :commit:`(patch) <e89f0a65581f82a5740bfe989136cea75d09cd67>` |
| 1914 |
|
| 1915 |
August 16, 2006 - :cve:`2007-0404` |
| 1916 |
---------------------------------- |
| 1917 |
|
| 1918 |
Filename validation issue in translation framework. `Full description |
| 1919 |
<https://www.djangoproject.com/weblog/2006/aug/16/compilemessages/>`__ |
| 1920 |
|
| 1921 |
Versions affected |
| 1922 |
~~~~~~~~~~~~~~~~~ |
| 1923 |
|
| 1924 |
* Django 0.90 :commit:`(patch) <6eefa521be3c658dc0b38f8d62d52e9801e198ab>` |
| 1925 |
* Django 0.91 :commit:`(patch) <d31e39173c29537e6a1613278c93634c18a3206e>` |
| 1926 |
* Django 0.95 :commit:`(patch) <a132d411c6986418ee6c0edc331080aa792fee6e>` |
| 1927 |
(released January 21 2007) |