Skip to main content

Test Results

mramshaw/Cloud_Django_3:requirements.txt

Vulnerabilities

 15 via 16 paths

Dependencies

 12

Source

 GitHub

Commit

 4ce33d4a

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 2
  • 3
  • 10
Status
  • 15
  • 0
  • 0

critical severity

SQL Injection

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.15.

Overview

Affected versions of this package are vulnerable to SQL Injection via the QuerySet.values() and values_list() methods on models with a JSONField. An attacker can exploit this vulnerability through column aliases by using a maliciously crafted JSON object object key as a passed *arg.

Remediation

Upgrade django to version 4.2.15, 5.0.8 or higher.

References

SQL Injection vulnerability report

critical severity

SQL Injection

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.17.

Overview

Affected versions of this package are vulnerable to SQL Injection via the django.db.models.fields.json.HasKey lookup on Oracle, if untrusted data is used as a lhs value. An attacker can manipulate SQL queries and access or alter database information.

Note: Applications that use the jsonfield.has_key lookup through the __ syntax are unaffected.

Remediation

Upgrade django to version 4.2.17, 5.0.10, 5.1.4 or higher.

References

SQL Injection vulnerability report

high severity
new

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.20.

Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the django.utils.text.wrap() function and wordwrap template filter. When either is supplied an excessively long string it may render the application unresponsive.

Remediation

Upgrade django to version 4.2.20, 5.0.13, 5.1.7 or higher.

References

Allocation of Resources Without Limits or Throttling vulnerability report

high severity

Uncontrolled Recursion

  • Vulnerable module: sqlparse
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25 › sqlparse@0.4.4
    Remediation: Upgrade to django@4.1.12.

Overview

Affected versions of this package are vulnerable to Uncontrolled Recursion due to the parsing of heavily nested lists. An attacker can cause the application to crash by submitting a specially crafted list that triggers a RecursionError.

Note: The impact depends on the use, so anyone parsing a user input with sqlparse.parse() is affected.

PoC


import sqlparse
sqlparse.parse('[' * 10000 + ']' * 10000)

Remediation

Upgrade sqlparse to version 0.5.0 or higher.

References

Uncontrolled Recursion vulnerability report

high severity

Command Injection

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.17.

Overview

Affected versions of this package are vulnerable to Command Injection via certain inputs containing large sequences of nested incomplete HTML entities submitted to the strip_tags function and striptags template filter. An attacker can cause the application to consume excessive resources.

Remediation

Upgrade django to version 4.2.17, 5.0.10, 5.1.4 or higher.

References

Command Injection vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.14.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) in django.utils.translation.get_supported_language_variant() function due to improper user input validation. An attacker can exploit this vulnerability by using very long strings containing specific characters. Exploiting this vulnerability could lead to a system crash.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade django to version 4.2.14, 5.0.7 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.14.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) via the in django.utils.html.urlize() and django.utils.html.urlizetrunc() functions. If certain inputs with a very large number of brackets are provided, this could lead to a system crash.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade django to version 4.2.14, 5.0.7 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.15.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) via very large inputs with a specific sequence of characters in the urlize() and urlizetrunc() template filters.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade django to version 4.2.15, 5.0.8 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.15.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) via certain inputs with a very large number of Unicode characters in the urlize and urlizetrunc template filters, and the AdminURLFieldWidget widget.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade django to version 4.2.15, 5.0.8 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.16.

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) due to not accounting for very large inputs involving intermediate ;s, in the django.utils.html.urlize() and django.utils.html.urlizetrunc() template filter functions.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade django to version 4.2.16, 5.0.9, 5.1.1 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Directory Traversal

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.14.

Overview

Affected versions of this package are vulnerable to Directory Traversal via the derived classes of the django.core.files.storage.Storage base class which override generate_filename() without replicating the file path validations existing in the parent class. This allows potential access to out of scope data via certain inputs when calling save() method.

Note: Built-in Storage sub-classes were not affected by this vulnerability.

Details

A Directory Traversal attack (also known as path traversal) aims to access files and directories that are stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and its variations, or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system, including application source code, configuration, and other critical system files.

Directory Traversal vulnerabilities can be generally divided into two types:

  • Information Disclosure: Allows the attacker to gain information about the folder structure or read the contents of sensitive files on the system.

st is a module for serving static files on web pages, and contains a vulnerability of this type. In our example, we will serve files from the public route.

If an attacker requests the following URL from our server, it will in turn leak the sensitive private key of the root user.

curl http://localhost:8080/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/root/.ssh/id_rsa

Note %2e is the URL encoded version of . (dot).

  • Writing arbitrary files: Allows the attacker to create or replace existing files. This type of vulnerability is also known as Zip-Slip.

One way to achieve this is by using a malicious zip archive that holds path traversal filenames. When each filename in the zip archive gets concatenated to the target extraction folder, without validation, the final path ends up outside of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicious file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:

2018-04-15 22:04:29 .....           19           19  good.txt
2018-04-15 22:04:42 .....           20           20  ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade django to version 4.2.14, 5.0.7 or higher.

References

Directory Traversal vulnerability report

medium severity

Uncontrolled Resource Consumption

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.15.

Overview

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption via the floatformat() template filter, when given a string representation of a number in scientific notation with a large exponent.

Remediation

Upgrade django to version 4.2.15, 5.0.8 or higher.

References

Uncontrolled Resource Consumption vulnerability report

medium severity

Infinite loop

  • Vulnerable module: zipp
  • Introduced through: gunicorn@23.0.0 and uvicorn@0.22.0

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › gunicorn@23.0.0 › importlib-metadata@6.7.0 › zipp@3.15.0
  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › uvicorn@0.22.0 › click@8.1.8 › importlib-metadata@6.7.0 › zipp@3.15.0

Overview

Affected versions of this package are vulnerable to Infinite loop where an attacker can cause the application to stop responding by initiating a loop through functions affecting the Path module, such as joinpath, the overloaded division operator, and iterdir.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade zipp to version 3.19.1 or higher.

References

Infinite loop vulnerability report

medium severity

Improper Check for Unusual or Exceptional Conditions

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.16.

Overview

Affected versions of this package are vulnerable to Improper Check for Unusual or Exceptional Conditions due to unhandled email sending failures in the django.contrib.auth.forms.PasswordResetForm class. This allows attackers to enumerate user email addresses by brute forcing password reset requests and observing the outcomes.

Remediation

Upgrade django to version 4.2.16, 5.0.9, 5.1.1 or higher.

References

Improper Check for Unusual or Exceptional Conditions vulnerability report

medium severity

Timing Attack

  • Vulnerable module: django
  • Introduced through: django@3.2.25

Detailed paths

  • Introduced through: mramshaw/Cloud_Django_3@mramshaw/Cloud_Django_3#4ce33d4ae574ddf1aab16806d427e0421faf0a72 › django@3.2.25
    Remediation: Upgrade to django@4.2.14.

Overview

Affected versions of this package are vulnerable to Timing Attack via the django.contrib.auth.backends.ModelBackend.authenticate() method. This allows remote attackers to enumerate users via a timing attack involving login requests for users with unusable passwords.

Remediation

Upgrade django to version 4.2.14, 5.0.7 or higher.

References

Timing Attack vulnerability report