Homepage
About Snyk

SQL Injection Affecting py3-django package, versions <1.11.23-r0

Severity

 Recommended
0.0
critical
0
10

Snyk's Security Team recommends NVD's CVSS assessment

    Threat Intelligence

    EPSS
    0.77% (82nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-ALPINE320-PY3DJANGO-7013809
  • published 23 May 2024
  • disclosed 9 Aug 2019
Report a new vulnerability Found a mistake?

Introduced: 9 Aug 2019

CVE-2019-14234 Open this link in a new tab
CWE-89 Open this link in a new tab

How to fix?

Upgrade Alpine:3.20 py3-django to version 1.11.23-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream py3-django package and not the py3-django package as distributed by Alpine. See How to fix? for Alpine:3.20 relevant fixed versions and status.

An issue was discovered in Django 1.11.x before 1.11.23, 2.1.x before 2.1.11, and 2.2.x before 2.2.4. Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of "OR 1=1" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function.

References