Skip to content
This repository has been archived by the owner on May 22, 2024. It is now read-only.

[Snyk: High] Django (Due 10/5/23) #792

Closed
Tracked by #137
cnlucas opened this issue Sep 6, 2023 · 0 comments · Fixed by #796
Closed
Tracked by #137

[Snyk: High] Django (Due 10/5/23) #792

cnlucas opened this issue Sep 6, 2023 · 0 comments · Fixed by #796
Assignees
Labels
Security: general General security concern or issue Security: high Remediate within 30 days Work: Back-end
Milestone

Comments

@cnlucas
Copy link
Member

cnlucas commented Sep 6, 2023

Introduced through
django@3.2.20, django-haystack@3.1.1 and others
Fixed in
django@3.2.21, @4.1.11, @4.2.5

Exploit maturity
No known exploit

Detailed paths and remediation

Introduced through: project@0.0.0 › django@3.2.20
Fix: Upgrade django to version 3.2.21 or 4.1.11 or 4.2.5

Introduced through: project@0.0.0 › django-haystack@3.1.1 › django@3.2.20
Fix: Pin django to version 3.2.21 or 4.1.11 or 4.2.5
Introduced through: project@0.0.0 › django-mptt@0.13.4 › django-js-asset@2.0.0 › django@3.2.20
Fix: Pin django to version 3.2.21 or 4.1.11 or 4.2.5

Security information
Factors contributing to the scoring:

Snyk: [CVSS 7.5](https://security.snyk.io/vuln/SNYK-PYTHON-DJANGO-5880505) - High Severity
NVD: Not available. NVD has not yet published its analysis.

Why are the scores different? Learn how Snyk evaluates vulnerability scores
Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) in the django.utils.encoding.uri_to_iri() function when processing inputs with a large number of Unicode characters.

Completion criteria:

  • Django is updated to 3.2.21
  • Vulnerability is no longer returned in Snyk test
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Security: general General security concern or issue Security: high Remediate within 30 days Work: Back-end
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants