Mprogrammer

**Name of the Vulnerable Software and Affected Versions** Django versions 4.2 through 4.2.15 Django versions 5.0 through 5.0.8 Django versions 5.1 through 5.1.0 **Description** The `urlize()` and `urlizetrunc()` template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters. This issue can be exploited by an attacker to cause a denial-of-service. **Recommendations** Django versions 4.2 through 4.2.15: Update to version 4.2.16. Django versions 5.0 through 5.0.8: Update to version 5.0.9. Django versions 5.1 through 5.1.0: Update to version 5.1.1. As a temporary workaround, consider disabling the `urlize()` and `urlizetrunc()` functions until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Django versions 4.2 through 4.2.14 Django versions 5.0 through 5.0.7 **Description** The issue is related to the `urlize()` and `urlizetrunc()` template filters in Django, which can be subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters. This can be exploited by a remote attacker to cause a denial of service. The vulnerability is associated with a mismatch in the length parameters of the input data. A bounty of $2,162 was paid for the discovery of this issue. **Recommendations** For Django versions 4.2 through 4.2.14, update to version 4.2.15 or later. For Django versions 5.0 through 5.0.7, update to version 5.0.8 or later. As a temporary workaround, consider restricting the use of the `urlize()` and `urlizetrunc()` template filters until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** Django versions 4.2 through 4.2.13 Django versions 5.0 through 5.0.6 **Description** The issue is related to the `get supported language variant()` function in Django, which can be subject to a potential denial-of-service attack when used with very long strings containing specific characters. This could allow a remote attacker to cause a denial of service. **Recommendations** For Django versions 4.2 through 4.2.13, update to version 4.2.14 or later. For Django versions 5.0 through 5.0.6, update to version 5.0.7 or later. As a temporary workaround, consider restricting the input to the `get supported language variant()` function to prevent very long strings from being processed.

**Name of the Vulnerable Software and Affected Versions** REXML gem versions prior to 3.3.3 **Description** The REXML gem has some DoS vulnerabilities when it parses an XML that has many specific characters, such as whitespace characters, `&gt;` and `]&gt;`, or `<`, `0` and `%>`. This vulnerability is related to uncontrolled resource consumption and can be exploited by a remote attacker to cause a denial of service. If you need to parse untrusted XMLs, you may be impacted by these vulnerabilities. **Recommendations** For REXML gem versions prior to 3.3.3, upgrade to version 3.3.3 or later to fix these vulnerabilities. As a temporary workaround, consider not parsing untrusted XMLs to minimize the risk of exploitation. Restricting the parsing of XMLs with many specific characters can also help mitigate the issue.

Name of the Vulnerable Software and Affected Versions: REXML versions prior to 3.3.1 REXML versions prior to 3.2.7 Description: The issue is related to denial-of-service vulnerabilities in the REXML gem for Ruby. When parsing XML with many specific characters, such as `<`, `0`, and `%>`, the gem may be impacted. Users who need to parse untrusted XMLs may be affected by these vulnerabilities. Recommendations: For REXML versions prior to 3.3.1, upgrade to version 3.3.2 or later to fix the vulnerabilities. For REXML versions prior to 3.2.7, upgrade to version 3.2.7 or later to fix the vulnerability. As a temporary workaround, consider avoiding the parsing of untrusted XML strings until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Django versions 3.2 before 3.2.23 Django versions 4.1 before 4.1.13 Django versions 4.2 before 4.2.7 **Description** The issue is related to the NFKC normalization being slow on Windows, which can lead to a potential denial of service (DoS) attack via certain inputs with a very large number of Unicode characters. This affects the `django.contrib.auth.forms.UsernameField`, making it subject to exploitation. The vulnerability is related to unlimited resource allocation, which can be exploited by a remote attacker to cause a denial of service. **Recommendations** For Django versions 3.2 before 3.2.23, update to version 3.2.23 or later to resolve the issue. For Django versions 4.1 before 4.1.13, update to version 4.1.13 or later to resolve the issue. For Django versions 4.2 before 4.2.7, update to version 4.2.7 or later to resolve the issue. As a temporary workaround, consider restricting the use of the `UsernameField` in the affected versions to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Django versions 3.2 through 3.2.20 Django versions 4.1 through 4.1.10 Django versions 4.2 through 4.2.4 **Description** The issue is related to the `django.utils.encoding.uri to iri()` component of the Django web application platform, which is vulnerable to a potential denial of service (DoS) attack due to incorrect input validation. This vulnerability can be exploited by a remote attacker, allowing them to cause a denial of service. The attack is possible via certain inputs with a very large number of Unicode characters. **Recommendations** For Django versions 3.2 through 3.2.20, update to version 3.2.21 or later. For Django versions 4.1 through 4.1.10, update to version 4.1.11 or later. For Django versions 4.2 through 4.2.4, update to version 4.2.5 or later. As a temporary workaround, consider restricting the input to the `uri to iri()` function to prevent large amounts of Unicode characters.

Name of the Vulnerable Software and Affected Versions: REXML versions prior to 3.2.6 REXML versions prior to 3.3.1 REXML versions prior to 3.3.2 REXML versions prior to 3.3.3 Description: The REXML gem has a denial of service vulnerability when it parses an XML that has many `<`s in an attribute value. Those who need to parse untrusted XMLs may be impacted by this vulnerability. Recommendations: For REXML versions prior to 3.2.6, update to REXML gem 3.2.7 or later. For REXML versions prior to 3.3.1, update to REXML gem 3.3.2 or later. For REXML versions prior to 3.3.2, update to REXML gem 3.3.3 or later. As a temporary workaround, do not parse untrusted XMLs.