Python/django/1.2.2
A high-level Python web framework that encourages rapid development and clean, pragmatic design.
https://pypi.org/project/django
BSD
32 Security Vulnerabilities
Django denial of service via file upload naming
- https://nvd.nist.gov/vuln/detail/CVE-2014-0481
- https://www.djangoproject.com/weblog/2014/aug/20/security/
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
- http://www.debian.org/security/2014/dsa-3010
- https://github.com/django/django/commit/26cd48e166ac4d84317c8ee6d63ac52a87e8da99
- https://github.com/django/django/commit/30042d475bf084c6723c6217a21598d9247a9c41
- https://github.com/django/django/commit/dd0c3f4ee1a30c1a1e6055061c6ba6e58c6b54d1
- https://github.com/advisories/GHSA-296w-6qhq-gf92
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a denial of service (CPU consumption) by unloading a multiple files with the same name.
Improper Input Validation in Django
- https://nvd.nist.gov/vuln/detail/CVE-2019-3498
- https://github.com/advisories/GHSA-337x-4q8g-prc5
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/forum/#!topic/django-announce/VYU7xQQTEPQ
- https://lists.debian.org/debian-lts-announce/2019/01/msg00005.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVXDOVCXLD74SHR2BENGCE2OOYYYWJHZ/
- https://usn.ubuntu.com/3851-1/
- https://www.debian.org/security/2019/dsa-4363
- https://www.djangoproject.com/weblog/2019/jan/04/security-releases/
- http://www.securityfocus.com/bid/106453
- https://web.archive.org/web/20200227094237/http://www.securityfocus.com/bid/106453
In Django 1.11.x before 1.11.18, 2.0.x before 2.0.10, and 2.1.x before 2.1.5, an Improper Neutralization of Special Elements in Output Used by a Downstream Component issue exists in django.views.defaults.page_not_found()
, leading to content spoofing (in a 404 error page) if a user fails to recognize that a crafted URL has malicious content.
Moderate severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2011-4137
- https://github.com/advisories/GHSA-3jqw-crqj-w8qw
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://hermes.opensuse.org/messages/14700881
- https://www.djangoproject.com/weblog/2011/sep/09/
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://openwall.com/lists/oss-security/2011/09/15/5
- http://secunia.com/advisories/46614
- http://www.debian.org/security/2011/dsa-2332
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.
Django Image Field Vulnerable to Image Decompression Bombs
- https://nvd.nist.gov/vuln/detail/CVE-2012-3443
- https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/
- https://github.com/django/django/commit/9ca0ff6268eeff92d0d0ac2c315d4b6a8e229155
- https://github.com/django/django/commit/da33d67181b53fe6cc737ac1220153814a1509f6
- https://www.debian.org/security/2012/dsa-2529
- https://www.mandriva.com/security/advisories?name=MDVSA-2012:143
- https://www.openwall.com/lists/oss-security/2012/07/31/1
- https://www.openwall.com/lists/oss-security/2012/07/31/2
- https://www.ubuntu.com/usn/USN-1560-1
- https://github.com/advisories/GHSA-59w8-4wm2-4xw8
The django.forms.ImageField
class in the form system in Django before 1.3.2 and 1.4.x before 1.4.1 completely decompresses image data during image validation, which allows remote attackers to cause a denial of service (memory consumption) by uploading an image file.
Moderate severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2011-0696
- https://github.com/advisories/GHSA-5j2h-h5hg-3wf8
- https://bugzilla.redhat.com/show_bug.cgi?id=676357
- http://lists.fedoraproject.org/pipermail/package-announce/2011-February/054207.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-February/054208.html
- http://openwall.com/lists/oss-security/2011/02/09/6
- http://secunia.com/advisories/43230
- http://secunia.com/advisories/43297
- http://secunia.com/advisories/43382
- http://secunia.com/advisories/43426
- http://www.debian.org/security/2011/dsa-2163
- http://www.djangoproject.com/weblog/2011/feb/08/security/
- http://www.mandriva.com/security/advisories?name=MDVSA-2011:031
- http://www.securityfocus.com/bid/46296
- http://www.ubuntu.com/usn/USN-1066-1
- http://www.vupen.com/english/advisories/2011/0372
- http://www.vupen.com/english/advisories/2011/0388
- http://www.vupen.com/english/advisories/2011/0429
- http://www.vupen.com/english/advisories/2011/0439
- http://www.vupen.com/english/advisories/2011/0441
Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a combination of browser plugins and redirects,
a related issue to CVE-2011-0447.
Django Middleware Enables Session Hijacking
- https://nvd.nist.gov/vuln/detail/CVE-2014-0482
- https://www.djangoproject.com/weblog/2014/aug/20/security/
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
- http://www.debian.org/security/2014/dsa-3010
- https://github.com/django/django/commit/0268b855f9eab3377f2821164ef3e66037789e09
- https://github.com/django/django/commit/5307ce565fbedb9cc27cbe7c757b41a00438d37c
- https://github.com/django/django/commit/c9e3b9949cd55f090591fbdc4a114fcb8368b6d9
- https://github.com/django/django/commit/dd68f319b365f6cb38c5a6c106faf4f6142d7d88
- https://github.com/django/django/blob/aa3cb3f37265be37d892e2b391ff023e9caee2a4/docs/releases/1.5.9.txt#L42
- https://github.com/advisories/GHSA-625g-gx8c-xcmg
The contrib.auth.middleware.RemoteUserMiddleware
middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend
backend, allows remote authenticated users to hijack web sessions via vectors related to the REMOTE_USER
header.
Django Cross-site Scripting Vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2015-2241
- https://code.djangoproject.com/ticket/24461
- https://www.djangoproject.com/weblog/2015/mar/09/security-releases/
- https://github.com/django/django/commit/2654e1b93923bac55f12b4e66c5e39b16695ace5
- https://github.com/django/django/commit/82c9169077a066995e3b00aac551bf1c8a89d98a
- https://web.archive.org/web/20150523054951/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:109/?name=MDVSA-2015:109
- https://web.archive.org/web/20171112005349/http://www.securityfocus.com/bid/73095
- https://github.com/advisories/GHSA-6565-fg86-6jcx
Cross-site scripting (XSS) vulnerability in the contents function in admin/helpers.py
in Django before 1.7.6 and 1.8 before 1.8b2 allows remote attackers to inject arbitrary web script or HTML via a model attribute in ModelAdmin.readonly_fields
, as demonstrated by an @property
.
Path Traversal in Django
- https://nvd.nist.gov/vuln/detail/CVE-2021-33203
- https://github.com/advisories/GHSA-68w8-qjq3-2gfm
- https://docs.djangoproject.com/en/3.2/releases/security/
- https://groups.google.com/forum/#!forum/django-announce
- https://www.djangoproject.com/weblog/2021/jun/02/security-releases/
- https://security.netapp.com/advisory/ntap-20210727-0004/
- https://github.com/django/django/commit/053cc9534d174dc89daba36724ed2dcb36755b90
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B4SQG2EAF4WCI2SLRL6XRDJ3RPK3ZRDV/
- https://github.com/django/django/commit/20c67a0693c4ede2b09af02574823485e82e4c8f
- https://github.com/django/django/commit/dfaba12cda060b8b292ae1d271b44bf810b1c5b9
Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.
Django Allows Redirect via Data URL
- https://nvd.nist.gov/vuln/detail/CVE-2012-3442
- https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/
- http://www.debian.org/security/2012/dsa-2529
- http://www.openwall.com/lists/oss-security/2012/07/31/1
- http://www.openwall.com/lists/oss-security/2012/07/31/2
- http://www.ubuntu.com/usn/USN-1560-1
- https://github.com/django/django/commit/4dea4883e6c50d75f215a6b9bcbd95273f57c72d
- https://github.com/django/django/commit/e34685034b60be1112160e76091e5aee60149fa1
- https://github.com/advisories/GHSA-78vx-ggch-wghm
The (1) django.http.HttpResponseRedirect
and (2) django.http.HttpResponsePermanentRedirect
classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data:
URL.
High severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2011-0698
- https://github.com/advisories/GHSA-7g9h-c88w-r7h2
- http://openwall.com/lists/oss-security/2011/02/09/6
- http://secunia.com/advisories/43230
- http://www.djangoproject.com/weblog/2011/feb/08/security/
- http://www.mandriva.com/security/advisories?name=MDVSA-2011:031
- http://www.securityfocus.com/bid/46296
- http://www.vupen.com/english/advisories/2011/0372
- http://www.vupen.com/english/advisories/2011/0439
Directory traversal vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 on Windows might allow remote attackers to read or execute files via a / (slash) character in a key in a session cookie, related to session replays.
Django WSGI Header Spoofing Vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2015-0219
- https://www.djangoproject.com/weblog/2015/jan/13/security/
- http://advisories.mageia.org/MGASA-2015-0026.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148485.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148608.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148696.html
- http://lists.opensuse.org/opensuse-updates/2015-04/msg00001.html
- http://lists.opensuse.org/opensuse-updates/2015-09/msg00035.html
- http://www.ubuntu.com/usn/USN-2469-1
- https://github.com/django/django/commit/41b4bc73ee0da7b2e09f4af47fc1fd21144c710f
- https://github.com/django/django/commit/4f6fffc1dc429f1ad428ecf8e6620739e8837450
- https://github.com/django/django/commit/d7597b31d5c03106eeba4be14a33b32a5e25f4ee
- https://github.com/django/daphne/blob/e49c39a4e5fac8ec170dd653641a9e90844fd3f1/daphne/http_protocol.py#L151
- https://web.archive.org/web/20150128111656/http://secunia.com/advisories/62285
- https://web.archive.org/web/20150128111656/http://secunia.com/advisories/62309
- https://web.archive.org/web/20150523054951/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:109/?name=MDVSA-2015:109
- https://web.archive.org/web/20150523054953/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:036/?name=MDVSA-2015:036
- https://web.archive.org/web/20151104201446/http://secunia.com/advisories/62718
- https://github.com/advisories/GHSA-7qfw-j7hp-v45g
Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 allows remote attackers to spoof WSGI headers by using an _
(underscore) character instead of a -
(dash) character in an HTTP header, as demonstrated by an X-Auth_User
header.
Moderate severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2010-4535
- https://github.com/advisories/GHSA-7wph-fc4w-wqp2
- https://bugzilla.redhat.com/show_bug.cgi?id=665373
- http://code.djangoproject.com/changeset/15032
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html
- http://secunia.com/advisories/42715
- http://secunia.com/advisories/42827
- http://secunia.com/advisories/42913
- http://www.djangoproject.com/weblog/2010/dec/22/security/
- http://www.openwall.com/lists/oss-security/2010/12/23/4
- http://www.openwall.com/lists/oss-security/2011/01/03/5
- http://www.securityfocus.com/bid/45563
- http://www.ubuntu.com/usn/USN-1040-1
- http://www.vupen.com/english/advisories/2011/0048
- http://www.vupen.com/english/advisories/2011/0098
The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.
Django Reuses Cached CSRF Token
- https://nvd.nist.gov/vuln/detail/CVE-2014-0473
- https://www.djangoproject.com/weblog/2014/apr/21/security/
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
- http://rhn.redhat.com/errata/RHSA-2014-0456.html
- http://rhn.redhat.com/errata/RHSA-2014-0457.html
- http://www.debian.org/security/2014/dsa-2934
- http://www.ubuntu.com/usn/USN-2169-1
- https://github.com/advisories/GHSA-89hj-xfx5-7q66
The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to bypass CSRF protections by reading the CSRF cookie for anonymous users.
Cross-site scripting in django
- https://nvd.nist.gov/vuln/detail/CVE-2011-0697
- https://github.com/advisories/GHSA-8m3r-rv5g-fcpq
- https://bugzilla.redhat.com/show_bug.cgi?id=676359
- http://lists.fedoraproject.org/pipermail/package-announce/2011-February/054207.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-February/054208.html
- http://openwall.com/lists/oss-security/2011/02/09/6
- http://secunia.com/advisories/43230
- http://secunia.com/advisories/43297
- http://secunia.com/advisories/43382
- http://secunia.com/advisories/43426
- http://www.debian.org/security/2011/dsa-2163
- http://www.djangoproject.com/weblog/2011/feb/08/security/
- http://www.mandriva.com/security/advisories?name=MDVSA-2011:031
- http://www.securityfocus.com/bid/46296
- http://www.ubuntu.com/usn/USN-1066-1
- http://www.vupen.com/english/advisories/2011/0372
- http://www.vupen.com/english/advisories/2011/0388
- http://www.vupen.com/english/advisories/2011/0429
- http://www.vupen.com/english/advisories/2011/0439
- http://www.vupen.com/english/advisories/2011/0441
- https://github.com/django/django/commit/1966786d2dde73e17f39cf340eb33fcb5d73904e
- https://github.com/django/django/commit/1f814a9547842dcfabdae09573055984af9d3fab
- https://github.com/django/django/commit/90be6ca20d607977dec234ec972b77b83955749b
- https://github.com/django/django/commit/a9cf3d23724ff6918103e86aa863eadd1fab811d
- http://www.djangoproject.com/weblog/2011/feb/08/security
Cross-site scripting (XSS) vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 might allow remote attackers to inject arbitrary web script or HTML via a filename associated with a file upload.
Django Cross-site scripting Vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2016-6186
- https://github.com/django/django/commit/d03bf6fe4e9bf5b07de62c1a271c4b41a7d3d158
- https://github.com/django/django/commit/f68e5a99164867ab0e071a936470958ed867479d
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DMLLFAUT4J4IP4P2KI4NOVWRMHA22WUJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KHHPN6MISX5I6UTXQHYLPTLEEUE6WDXW/
- https://www.djangoproject.com/weblog/2016/jul/18/security-releases/
- https://www.exploit-db.com/exploits/40129/
- http://packetstormsecurity.com/files/137965/Django-3.3.0-Script-Insertion.html
- http://rhn.redhat.com/errata/RHSA-2016-1594.html
- http://rhn.redhat.com/errata/RHSA-2016-1595.html
- http://rhn.redhat.com/errata/RHSA-2016-1596.html
- http://seclists.org/fulldisclosure/2016/Jul/53
- http://www.debian.org/security/2016/dsa-3622
- http://www.ubuntu.com/usn/USN-3039-1
- http://www.vulnerability-lab.com/get_content.php?id=1869
- https://web.archive.org/web/20201022155237/http://www.securityfocus.com/archive/1/538947/100/0/threaded
- https://web.archive.org/web/20210123154652/http://www.securityfocus.com/bid/92058
- https://web.archive.org/web/20211204042848/http://www.securitytracker.com/id/1036338
- https://github.com/advisories/GHSA-c8c8-9472-w52h
- https://github.com/django/django/commit/6fa150b2f8b601668083042324c4add534143cb1
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DMLLFAUT4J4IP4P2KI4NOVWRMHA22WUJ
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KHHPN6MISX5I6UTXQHYLPTLEEUE6WDXW
- https://www.djangoproject.com/weblog/2016/jul/18/security-releases
- https://www.exploit-db.com/exploits/40129
Cross-site scripting (XSS) vulnerability in the dismissChangeRelatedObjectPopup
function in contrib/admin/static/admin/js/admin/RelatedObjectLookups.js
in Django before 1.8.14, 1.9.x before 1.9.8, and 1.10.x before 1.10rc1 allows remote attackers to inject arbitrary web script or HTML via vectors involving unsafe usage of Element.innerHTML.
Django CSRF Protection Bypass
- https://nvd.nist.gov/vuln/detail/CVE-2016-7401
- https://www.djangoproject.com/weblog/2016/sep/26/security-releases/
- http://rhn.redhat.com/errata/RHSA-2016-2038.html
- http://rhn.redhat.com/errata/RHSA-2016-2039.html
- http://rhn.redhat.com/errata/RHSA-2016-2040.html
- http://rhn.redhat.com/errata/RHSA-2016-2041.html
- http://rhn.redhat.com/errata/RHSA-2016-2042.html
- http://rhn.redhat.com/errata/RHSA-2016-2043.html
- http://www.debian.org/security/2016/dsa-3678
- http://www.ubuntu.com/usn/USN-3089-1
- https://web.archive.org/web/20200227223637/http://www.securityfocus.com/bid/93182
- https://web.archive.org/web/20210927195154/http://www.securitytracker.com/id/1036899
- https://github.com/advisories/GHSA-crhm-qpjc-cm64
- https://github.com/django/django/commit/6fe846a8f08dc959003f298b5407e321c6fe3735
- https://github.com/django/django/commit/6118ab7d0676f0d622278e5be215f14fb5410b6a
- https://github.com/django/django/commit/d1bc980db1c0fffd6d60677e62f70beadb9fe64a
- https://www.djangoproject.com/weblog/2016/sep/26/security-releases
The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.
Django Incorrectly Validates URLs
- https://nvd.nist.gov/vuln/detail/CVE-2014-0480
- https://www.djangoproject.com/weblog/2014/aug/20/security/
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
- http://www.debian.org/security/2014/dsa-3010
- https://github.com/django/django/commit/45ac9d4fb087d21902469fc22643f5201d41a0cd
- https://github.com/django/django/commit/c2fe73133b62a1d9e8f7a6b43966570b14618d7e
- https://github.com/django/django/commit/da051da8df5e69944745072611351d4cfc6435d5
- https://web.archive.org/web/20140918034351/http://www.securityfocus.com/bid/69425
- https://github.com/advisories/GHSA-f7cm-ccfp-3q4r
The core.urlresolvers.reverse
function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a //
(slash slash) in a URL, which triggers a scheme-relative URL to be generated.
Django User Enumeration Vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2016-2513
- https://github.com/django/django/commit/67b46ba7016da2d259c1ecc7d666d11f5e1cfaab
- https://www.djangoproject.com/weblog/2016/mar/01/security-releases/
- http://rhn.redhat.com/errata/RHSA-2016-0502.html
- http://rhn.redhat.com/errata/RHSA-2016-0504.html
- http://rhn.redhat.com/errata/RHSA-2016-0505.html
- http://rhn.redhat.com/errata/RHSA-2016-0506.html
- http://www.debian.org/security/2016/dsa-3544
- http://www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html
- http://www.securityfocus.com/bid/83878
- http://www.securitytracker.com/id/1035152
- http://www.ubuntu.com/usn/USN-2915-1
- http://www.ubuntu.com/usn/USN-2915-2
- http://www.ubuntu.com/usn/USN-2915-3
- https://github.com/advisories/GHSA-fp6p-5xvw-m74f
- https://web.archive.org/web/20160322001143/http://www.securitytracker.com/id/1035152
- https://web.archive.org/web/20200228001222/http://www.securityfocus.com/bid/83878
- https://github.com/django/django/commit/af7d09b0c5c6ab68e629fd9baf736f9dd203b18e
- https://github.com/django/django/commit/f4e6e02f7713a6924d16540be279909ff4091eb6
- https://www.djangoproject.com/weblog/2016/mar/01/security-releases
The password hasher in contrib/auth/hashers.py
in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to enumerate users via a timing attack involving login requests.
Moderate severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2010-4534
- https://github.com/advisories/GHSA-fwr5-q9rx-294f
- https://bugzilla.redhat.com/show_bug.cgi?id=665373
- http://archives.neohapsis.com/archives/fulldisclosure/2010-12/0580.html
- http://code.djangoproject.com/changeset/15031
- http://evilpacket.net/2010/dec/22/information-leakage-django-administrative-interfac/
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html
- http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html
- http://ngenuity-is.com/advisories/2010/dec/22/information-leakage-in-django-administrative-inter/
- http://secunia.com/advisories/42715
- http://secunia.com/advisories/42827
- http://secunia.com/advisories/42913
- http://www.djangoproject.com/weblog/2010/dec/22/security/
- http://www.openwall.com/lists/oss-security/2010/12/23/4
- http://www.openwall.com/lists/oss-security/2011/01/03/5
- http://www.securityfocus.com/archive/1/515446
- http://www.securityfocus.com/bid/45562
- http://www.ubuntu.com/usn/USN-1040-1
- http://www.vupen.com/english/advisories/2011/0048
- http://www.vupen.com/english/advisories/2011/0098
The administrative interface in django.contrib.admin in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not properly restrict use of the query string to perform certain object filtering, which allows remote authenticated users to obtain sensitive information via a series of requests containing regular expressions, as demonstrated by a createdbypassword_regex parameter.
Django Cross-site Scripting Vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2015-0220
- https://www.djangoproject.com/weblog/2015/jan/13/security/
- http://advisories.mageia.org/MGASA-2015-0026.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148485.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148608.html
- http://lists.opensuse.org/opensuse-updates/2015-04/msg00001.html
- http://lists.opensuse.org/opensuse-updates/2015-09/msg00035.html
- http://ubuntu.com/usn/usn-2469-1
- https://github.com/django/django/commit/4c241f1b710da6419d9dca160e80b23b82db7758
- https://github.com/django/django/commit/72e0b033662faa11bb7f516f18a132728aa0ae28
- https://github.com/django/django/commit/de67dedc771ad2edec15c1d00c083a1a084e1e89
- https://github.com/django/django/blob/4555a823fd57e261e1b19c778429473256c8ea08/docs/releases/1.4.18.txt#L34-L46
- https://web.archive.org/web/20150128111656/http://secunia.com/advisories/62285
- https://web.archive.org/web/20150523054951/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:109/?name=MDVSA-2015:109
- https://web.archive.org/web/20150523054953/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:036/?name=MDVSA-2015:036
- https://web.archive.org/web/20151104201446/http://secunia.com/advisories/62718
- https://github.com/advisories/GHSA-gv98-g628-m9x5
The django.util.http.is_safe_url
function in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 does not properly handle leading whitespaces, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL, related to redirect URLs, as demonstrated by a \njavascript:
URL.
Django Denial-of-service by filling session store
- https://nvd.nist.gov/vuln/detail/CVE-2015-5143
- https://github.com/advisories/GHSA-h582-2pch-3xv3
- https://security.gentoo.org/glsa/201510-06
- https://www.djangoproject.com/weblog/2015/jul/08/security-releases/
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172084.html
- http://lists.opensuse.org/opensuse-updates/2015-10/msg00043.html
- http://lists.opensuse.org/opensuse-updates/2015-10/msg00046.html
- http://rhn.redhat.com/errata/RHSA-2015-1678.html
- http://rhn.redhat.com/errata/RHSA-2015-1686.html
- http://www.debian.org/security/2015/dsa-3305
- http://www.oracle.com/technetwork/topics/security/bulletinoct2015-2511968.html
- http://www.securityfocus.com/bid/75666
- http://www.securitytracker.com/id/1032820
- http://www.ubuntu.com/usn/USN-2671-1
The session backends in Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (session store consumption) via multiple requests with unique session keys.
Moderate severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2011-4140
- https://github.com/advisories/GHSA-h95j-h2rv-qrg4
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://hermes.opensuse.org/messages/14700881
- https://www.djangoproject.com/weblog/2011/sep/09/
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://secunia.com/advisories/46614
- http://www.debian.org/security/2011/dsa-2332
The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.
SQL injection in Django
- https://nvd.nist.gov/vuln/detail/CVE-2020-7471
- https://github.com/advisories/GHSA-hmr4-m2h5-33qx
- https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136
- https://docs.djangoproject.com/en/3.0/releases/security/
- https://groups.google.com/forum/#!topic/django-announce/X45S86X5bZI
- https://www.djangoproject.com/weblog/2020/feb/03/security-releases/
- https://www.openwall.com/lists/oss-security/2020/02/03/1
- http://www.openwall.com/lists/oss-security/2020/02/03/1
- https://usn.ubuntu.com/4264-1/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/
- https://seclists.org/bugtraq/2020/Feb/30
- https://security.gentoo.org/glsa/202004-17
- https://security.netapp.com/advisory/ntap-20200221-0006/
- https://www.debian.org/security/2020/dsa-4629
- https://github.com/django/django/commit/001b0634cd309e372edb6d7d95d083d02b8e37bd
- https://github.com/django/django/commit/505826b469b16ab36693360da9e11fd13213421b
- https://github.com/django/django/commit/c67a368c16e4680b324b4f385398d638db4d8147
Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.
Django DoS in django.views.static.serve
- https://nvd.nist.gov/vuln/detail/CVE-2015-0221
- https://www.djangoproject.com/weblog/2015/jan/13/security/
- http://advisories.mageia.org/MGASA-2015-0026.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148485.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148608.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-January/148696.html
- http://lists.opensuse.org/opensuse-updates/2015-04/msg00001.html
- http://lists.opensuse.org/opensuse-updates/2015-09/msg00035.html
- http://ubuntu.com/usn/usn-2469-1
- https://github.com/django/django/commit/553779c4055e8742cc832ed525b9ee34b174934f
- https://github.com/django/django/commit/818e59a3f0fbadf6c447754d202d88df025f8f2a
- https://github.com/django/django/commit/d020da6646c5142bc092247d218a3d1ce3e993f7
- https://github.com/django/django/blob/9b9c805cedb08621bd5dc58a01a6478eb7cc49a9/docs/releases/1.4.18.txt#L48C1-L49C1
- https://web.archive.org/web/20150128111656/http://secunia.com/advisories/62285
- https://web.archive.org/web/20150128111656/http://secunia.com/advisories/62309
- https://web.archive.org/web/20150523054951/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:109/?name=MDVSA-2015:109
- https://web.archive.org/web/20150523054953/http://www.mandriva.com/en/support/security/advisories/advisory/MDVSA-2015:036/?name=MDVSA-2015:036
- https://web.archive.org/web/20151104201446/http://secunia.com/advisories/62718
- https://github.com/advisories/GHSA-jhjg-w2cp-5j44
- https://www.djangoproject.com/weblog/2015/jan/13/security
The django.views.static.serve
view in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 reads files an entire line at a time, which allows remote attackers to cause a denial of service (memory consumption) via a long line in a file.
Django XSS Vulnerability
- https://nvd.nist.gov/vuln/detail/CVE-2016-2512
- https://github.com/django/django/commit/c5544d289233f501917e25970c03ed444abbd4f0
- https://www.djangoproject.com/weblog/2016/mar/01/security-releases/
- http://rhn.redhat.com/errata/RHSA-2016-0502.html
- http://rhn.redhat.com/errata/RHSA-2016-0504.html
- http://rhn.redhat.com/errata/RHSA-2016-0505.html
- http://rhn.redhat.com/errata/RHSA-2016-0506.html
- http://www.debian.org/security/2016/dsa-3544
- http://www.oracle.com/technetwork/topics/security/bulletinapr2016-2952098.html
- http://www.ubuntu.com/usn/USN-2915-1
- http://www.ubuntu.com/usn/USN-2915-2
- http://www.ubuntu.com/usn/USN-2915-3
- https://web.archive.org/web/20210123090815/http://www.securityfocus.com/bid/83879
- https://web.archive.org/web/20210413200202/http://www.securitytracker.com/id/1035152
- https://github.com/advisories/GHSA-pw27-w7w4-9qc7
- https://github.com/django/django/commit/382ab137312961ad62feb8109d70a5a581fe8350
- https://github.com/django/django/commit/fc6d147a63f89795dbcdecb0559256470fff4380
- https://www.djangoproject.com/weblog/2016/mar/01/security-releases
The utils.http.is_safe_url function
in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks or possibly conduct cross-site scripting (XSS) attacks via a URL containing basic authentication, as demonstrated by http://mysite.example.com\@attacker.com
.
Django Vulnerable to HTTP Response Splitting Attack
- https://nvd.nist.gov/vuln/detail/CVE-2015-5144
- https://security.gentoo.org/glsa/201510-06
- https://www.djangoproject.com/weblog/2015/jul/08/security-releases/
- http://lists.fedoraproject.org/pipermail/package-announce/2015-November/172084.html
- http://lists.opensuse.org/opensuse-updates/2015-10/msg00043.html
- http://lists.opensuse.org/opensuse-updates/2015-10/msg00046.html
- http://www.debian.org/security/2015/dsa-3305
- http://www.oracle.com/technetwork/topics/security/bulletinoct2015-2511968.html
- http://www.ubuntu.com/usn/USN-2671-1
- https://github.com/django/django/commit/1ba1cdce7d58e6740fe51955d945b56ae51d072a
- https://github.com/django/django/commit/574dd5e0b0fbb877ae5827b1603d298edc9bb2a0
- https://github.com/django/django/commit/ae49b4d994656bc037513dcd064cb9ce5bb85649
- https://github.com/django/django/blob/4555a823fd57e261e1b19c778429473256c8ea08/docs/releases/1.4.21.txt#L30-L54
- https://web.archive.org/web/20150924150801/http://www.securitytracker.com/id/1032820
- https://web.archive.org/web/20200228050526/http://www.securityfocus.com/bid/75665
- https://github.com/advisories/GHSA-q5qw-4364-5hhm
- https://github.com/django/django/commit/8f9a4d3a2bc42f14bb437defd30c7315adbff22c
- https://www.djangoproject.com/weblog/2015/jul/08/security-releases
Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 uses an incorrect regular expression, which allows remote attackers to inject arbitrary headers and conduct HTTP response splitting attacks via a newline character in an (1) email message to the EmailValidator, a (2) URL to the URLValidator, or unspecified vectors to the (3) validateipv4address or (4) validate_slug validator.
Django Vulnerable to Cache Poisoning
- https://nvd.nist.gov/vuln/detail/CVE-2011-4139
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://hermes.opensuse.org/messages/14700881
- https://www.djangoproject.com/weblog/2011/sep/09/
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://www.debian.org/security/2011/dsa-2332
- https://github.com/django/django/commit/2f7fadc38efa58ac0a8f93f936b82332a199f396
- https://github.com/django/django/commit/c613af4d6485586c79d692b70a9acac429f3ca9d
- https://github.com/advisories/GHSA-rm2j-x595-q9cj
Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's HTTP Host header to construct a full URL in certain circumstances, which allows remote attackers to conduct cache poisoning attacks via a crafted request.
Django Potential account hijack via password reset form
- https://nvd.nist.gov/vuln/detail/CVE-2019-19844
- https://github.com/advisories/GHSA-vfq6-hq5r-27r6
- https://github.com/django/django/commit/5b1fbcef7a8bec991ebe7b2a18b5d5a95d72cb70
- https://github.com/django/django/commit/f4cff43bf921fcea6a29b726eb66767f67753fa2
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/forum/#!topic/django-announce/3oaB2rVH3a0
- https://seclists.org/bugtraq/2020/Jan/9
- https://security.netapp.com/advisory/ntap-20200110-0003/
- https://usn.ubuntu.com/4224-1/
- https://www.debian.org/security/2020/dsa-4598
- https://www.djangoproject.com/weblog/2019/dec/18/security-releases/
- http://packetstormsecurity.com/files/155872/Django-Account-Hijack.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HCM2DPUI7TOZWN4A6JFQFUVQ2XGE7GUD/
- https://security.gentoo.org/glsa/202004-17
- https://github.com/django/django/commit/302a4ff1e8b1c798aab97673909c7a3dfda42c26
- https://github.com/django/django/commit/4d334bea06cac63dc1272abcec545b85136cca0e
Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. (One mitigation in the new releases is to send password reset tokens only to the registered user email address.)
Uncontrolled Memory Consumption in Django
- https://nvd.nist.gov/vuln/detail/CVE-2019-6975
- https://github.com/advisories/GHSA-wh4h-v3f2-r2pp
- https://docs.djangoproject.com/en/dev/releases/security/
- https://groups.google.com/forum/#!topic/django-announce/WTwEAprR0IQ
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/66WMXHGBXD7GSM3PEXVCMCAGLMQYHZCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HVXDOVCXLD74SHR2BENGCE2OOYYYWJHZ/
- https://seclists.org/bugtraq/2019/Jul/10
- https://usn.ubuntu.com/3890-1/
- https://www.debian.org/security/2019/dsa-4476
- https://www.djangoproject.com/weblog/2019/feb/11/security-releases/
- https://www.openwall.com/lists/oss-security/2019/02/11/1
- http://www.securityfocus.com/bid/106964
- https://github.com/django/django/commit/0bbb560183fabf0533289700845dafa94951f227
- https://github.com/django/django/commit/1f42f82566c9d2d73aff1c42790d6b1b243f7676
- https://github.com/django/django/commit/40cd19055773705301c3428ed5e08a036d2091f3
- https://web.archive.org/web/20200227084713/http://www.securityfocus.com/bid/106964
Django 1.11.x before 1.11.19, 2.0.x before 2.0.11, and 2.1.x before 2.1.6 allows Uncontrolled Memory Consumption via a malicious attacker-supplied value to the django.utils.numberformat.format()
function.
Django Vulnerable to MySQL Injection
- https://nvd.nist.gov/vuln/detail/CVE-2014-0474
- https://www.djangoproject.com/weblog/2014/apr/21/security/
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.html
- http://rhn.redhat.com/errata/RHSA-2014-0456.html
- http://rhn.redhat.com/errata/RHSA-2014-0457.html
- http://www.debian.org/security/2014/dsa-2934
- http://www.ubuntu.com/usn/USN-2169-1
- https://github.com/django/django/commit/5f0829a27e85d89ad8c433f5c6a7a7d17c9e9292
- https://github.com/django/django/commit/985434fb1d6bf2335bf96c6ebf91c3674f1f399f
- https://github.com/django/django/commit/aa80f498de6d687e613860933ac58433ab71ea4b
- https://github.com/advisories/GHSA-wqjj-hx84-v449
The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 do not properly perform type conversion, which allows remote attackers to have unspecified impact and vectors, related to MySQL typecasting.
Moderate severity vulnerability that affects django
- https://nvd.nist.gov/vuln/detail/CVE-2011-4136
- https://github.com/advisories/GHSA-x88j-93vc-wpmp
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- https://hermes.opensuse.org/messages/14700881
- https://www.djangoproject.com/weblog/2011/sep/09/
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://openwall.com/lists/oss-security/2011/09/11/1
- http://openwall.com/lists/oss-security/2011/09/13/2
- http://secunia.com/advisories/46614
- http://www.debian.org/security/2011/dsa-2332
django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.
Django denial-of-service attack in the intcomma template filter
- https://nvd.nist.gov/vuln/detail/CVE-2024-24680
- https://docs.djangoproject.com/en/5.0/releases/security/
- https://groups.google.com/forum/#%21forum/django-announce
- https://www.djangoproject.com/weblog/2024/feb/06/security-releases/
- https://github.com/django/django/commit/16a8fe18a3b81250f4fa57e3f93f0599dc4895bc
- https://github.com/django/django/commit/55519d6cf8998fe4c8f5c8abffc2b10a7c3d14e9
- https://github.com/django/django/commit/572ea07e84b38ea8de0551f4b4eda685d91d09d2
- https://github.com/django/django/commit/c1171ffbd570db90ca206c30f8e2b9f691243820
- https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2024-28.yaml
- https://github.com/advisories/GHSA-xxj9-f6rv-m3x4
- https://docs.djangoproject.com/en/5.0/releases/security
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D2JIRXEDP4ZET5KFMAPPYSK663Q52NEX
- https://www.djangoproject.com/weblog/2024/feb/06/security-releases
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SN2PLJGYSAAG5KUVIUFJYKD3BLQ4OSN6
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZQJOMNRMVPCN5WMIZ7YSX5LQ7IR2NY4D
An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2. The intcomma template filter was subject to a potential denial-of-service attack when used with very long strings.
360 Other Versions
Version | License | Security | Released | |
---|---|---|---|---|
5.0.6 | BSD-3-Clause AND BSD | |||
5.0.5 | BSD-3-Clause AND BSD | |||
5.0.4 | BSD-3-Clause AND BSD | |||
5.0.3 | BSD-3-Clause AND BSD | |||
5.0.2 | BSD-3-Clause AND BSD | 1 | ||
5.0.1 | BSD-3-Clause AND BSD | 2 | ||
5.0 | BSD-3-Clause AND BSD | 2 | ||
4.2.13 | BSD-3-Clause AND BSD | |||
4.2.12 | BSD-3-Clause AND BSD | |||
4.2.11 | BSD-3-Clause AND BSD | |||
4.2.10 | BSD-3-Clause AND BSD | 1 | ||
4.2.9 | BSD-3-Clause AND BSD | 2 | ||
4.2.8 | BSD-3-Clause AND BSD | 2 | ||
4.2.7 | BSD-3-Clause AND BSD | 2 | ||
4.2.6 | BSD-3-Clause AND BSD | 3 | ||
4.2.5 | BSD-3-Clause AND BSD | 4 | ||
4.2.4 | BSD-3-Clause AND BSD | 5 | ||
4.2.3 | BSD-3-Clause AND BSD | 5 | ||
4.2.2 | BSD-3-Clause AND BSD | 6 | ||
4.2.1 | BSD-3-Clause AND BSD | 6 | ||
4.2 | BSD-3-Clause AND BSD | 6 | ||
4.1.13 | BSD-3-Clause AND BSD | |||
4.1.12 | BSD-3-Clause AND BSD | 1 | ||
4.1.11 | BSD-3-Clause AND BSD | 2 | ||
4.1.10 | BSD-3-Clause AND BSD | 3 | ||
4.1.9 | BSD-3-Clause AND BSD | 4 | ||
4.1.8 | BSD-3-Clause AND BSD | 4 | ||
4.1.7 | BSD-3-Clause AND BSD | 4 | ||
4.1.6 | BSD-3-Clause AND BSD | 4 | ||
4.1.5 | BSD-3-Clause AND BSD | 5 | ||
4.1.4 | BSD-3-Clause AND BSD | 5 | ||
4.1.3 | BSD-3-Clause AND BSD | 5 | ||
4.1.2 | BSD-3-Clause AND BSD | 5 | ||
4.1.1 | BSD-3-Clause AND BSD | 6 | ||
4.1 | BSD-3-Clause AND BSD | 6 | ||
4.0.10 | BSD-3-Clause AND BSD | 1 | ||
4.0.9 | BSD-3-Clause AND BSD | 1 | ||
4.0.8 | BSD-3-Clause AND BSD | 2 | ||
4.0.7 | BSD-3-Clause AND BSD | 3 | ||
4.0.6 | BSD-3-Clause AND BSD | 3 | 2022-07-04 - 07:57 | almost 2 years |
4.0.5 | BSD-3-Clause AND BSD | 4 | 2022-06-01 - 12:22 | almost 2 years |
4.0.4 | BSD-3-Clause AND BSD | 4 | 2022-04-11 - 07:53 | about 2 years |
4.0.3 | BSD-3-Clause AND BSD | 4 | 2022-03-01 - 08:47 | about 2 years |
4.0.2 | BSD-3-Clause AND BSD | 4 | 2022-02-01 - 07:56 | over 2 years |
4.0.1 | BSD-3-Clause AND BSD | 6 | 2022-01-04 - 09:53 | over 2 years |
4.0 | BSD-3-Clause AND BSD | 6 | 2021-12-07 - 09:19 | over 2 years |
3.2.25 | BSD-3-Clause AND BSD | |||
3.2.24 | BSD-3-Clause AND BSD | 1 | ||
3.2.23 | BSD-3-Clause AND BSD | 2 | ||
3.2.22 | BSD-3-Clause AND BSD | 3 | ||
3.2.21 | BSD-3-Clause AND BSD | 4 | ||
3.2.20 | BSD-3-Clause AND BSD | 5 | ||
3.2.19 | BSD-3-Clause AND BSD | 6 | ||
3.2.18 | BSD-3-Clause AND BSD | 6 | ||
3.2.17 | BSD-3-Clause AND BSD | 6 | ||
3.2.16 | BSD-3-Clause AND BSD | 7 | ||
3.2.15 | BSD-3-Clause AND BSD | 8 | ||
3.2.14 | BSD-3-Clause AND BSD | 8 | 2022-07-04 - 07:57 | almost 2 years |
3.2.13 | BSD-3-Clause AND BSD | 9 | 2022-04-11 - 07:52 | about 2 years |
3.2.12 | BSD-3-Clause AND BSD | 9 | 2022-02-01 - 07:56 | over 2 years |
3.2.11 | BSD-3-Clause AND BSD | 11 | 2022-01-04 - 09:53 | over 2 years |
3.2.10 | BSD-3-Clause AND BSD | 11 | 2021-12-07 - 07:34 | over 2 years |
3.2.9 | BSD-3-Clause AND BSD | 11 | 2021-11-01 - 09:31 | over 2 years |
3.2.8 | BSD-3-Clause AND BSD | 11 | 2021-10-05 - 07:46 | over 2 years |
3.2.7 | BSD-3-Clause AND BSD | 11 | 2021-09-01 - 05:57 | over 2 years |
3.2.6 | BSD-3-Clause AND BSD | 11 | 2021-08-02 - 06:28 | almost 3 years |
3.2.5 | BSD-3-Clause AND BSD | 11 | 2021-07-01 - 07:40 | almost 3 years |
3.2.4 | BSD-3-Clause AND BSD | 11 | 2021-06-02 - 08:54 | almost 3 years |
3.2.3 | BSD-3-Clause AND BSD | 13 | 2021-05-13 - 07:36 | about 3 years |
3.2.2 | BSD-3-Clause AND BSD | 13 | 2021-05-06 - 07:40 | about 3 years |
3.2.1 | BSD-3-Clause AND BSD | 13 | 2021-05-04 - 08:47 | about 3 years |
3.2 | BSD-3-Clause AND BSD | 13 | 2021-04-06 - 09:33 | about 3 years |
3.1.14 | BSD-3-Clause AND BSD | 1 | 2021-12-07 - 07:34 | over 2 years |
3.1.13 | BSD-3-Clause AND BSD | 1 | 2021-07-01 - 07:39 | almost 3 years |
3.1.12 | BSD-3-Clause AND BSD | 1 | 2021-06-02 - 08:53 | almost 3 years |
3.1.11 | BSD-3-Clause AND BSD | 3 | 2021-05-13 - 07:36 | about 3 years |
3.1.10 | BSD-3-Clause AND BSD | 3 | 2021-05-06 - 07:40 | about 3 years |
3.1.9 | BSD-3-Clause AND BSD | 3 | 2021-05-04 - 08:47 | about 3 years |
3.1.8 | BSD-3-Clause AND BSD | 3 | 2021-04-06 - 07:34 | about 3 years |
3.1.7 | BSD-3-Clause AND BSD | 3 | 2021-02-19 - 09:08 | about 3 years |
3.1.6 | BSD-3-Clause AND BSD | 3 | 2021-02-01 - 09:28 | over 3 years |
3.1.5 | BSD-3-Clause AND BSD | 4 | 2021-01-04 - 07:54 | over 3 years |
3.1.4 | BSD-3-Clause AND BSD | 4 | 2020-12-01 - 06:03 | over 3 years |
3.1.3 | BSD-3-Clause AND BSD | 4 | 2020-11-02 - 08:12 | over 3 years |
3.1.2 | BSD-3-Clause AND BSD | 4 | 2020-10-01 - 05:38 | over 3 years |
3.1.1 | BSD-3-Clause AND BSD | 4 | 2020-09-01 - 09:14 | over 3 years |
3.1 | BSD-3-Clause AND BSD | 6 | 2020-08-04 - 08:07 | almost 4 years |
3.0.14 | BSD | 3 | 2021-04-06 - 07:34 | about 3 years |
3.0.13 | BSD | 3 | 2021-02-19 - 09:08 | about 3 years |
3.0.12 | BSD | 3 | 2021-02-01 - 09:28 | over 3 years |
3.0.11 | BSD | 4 | 2020-11-02 - 08:12 | over 3 years |
3.0.10 | BSD | 4 | 2020-09-01 - 09:14 | over 3 years |
3.0.9 | BSD | 6 | 2020-08-03 - 07:23 | almost 4 years |
3.0.8 | BSD | 6 | 2020-07-01 - 04:49 | almost 4 years |
3.0.7 | BSD | 6 | 2020-06-03 - 09:36 | almost 4 years |
3.0.6 | BSD | 8 | 2020-05-04 - 05:26 | about 4 years |
3.0.5 | BSD | 8 | 2020-04-01 - 07:59 | about 4 years |
3.0.4 | BSD | 8 | 2020-03-04 - 09:31 | about 4 years |
3.0.3 | BSD | 9 | 2020-02-03 - 09:50 | over 4 years |
3.0.2 | BSD | 10 | 2020-01-02 - 07:22 | over 4 years |