Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security] Bump django from 1.11.10 to 1.11.21 #530

Closed
wants to merge 1 commit into from

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Jun 11, 2019

Bumps django from 1.11.10 to 1.11.21. This update includes security fixes.

Vulnerabilities fixed

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects django
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable.

Affected versions: >= 1.11, < 1.11.11

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects django
An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.

Affected versions: >= 1.11, < 1.11.11

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects django
django.middleware.common.CommonMiddleware in Django 1.11.x before 1.11.15 and 2.0.x before 2.0.8 has an Open Redirect.

Affected versions: >= 1.11.0, < 1.11.15

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects django
An issue was discovered in Django 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2. The clickable Current URL value displayed by the AdminURLFieldWidget displays the provided value without validating it as a safe URL. Thus, an unvalidated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link.

Affected versions: >= 1.11.0, < 1.11.21

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects django
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.

Affected versions: < 1.11.18

Sourced from The GitHub Security Advisory Database.

Memory exhaustion in django.utils.numberformat.format()
If django.utils.numberformat.format() -- used by contrib.admin as well as the the floatformat, filesizeformat, and intcomma templates filters -- received a Decimal with a large number of digits or a large exponent, it could lead to significant memory usage due to a call to '{:f}'.format().

Affected versions: >= 1.11.0, < 1.11.19; >= 2.0.0, < 2.0.11; >= 2.1.0, < 2.1.6

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects django
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.

Affected versions: < 1.11.19

Commits
  • bc1f79d [1.11.x] Bumped version for 1.11.21 release.
  • c238701 [1.11.x] Fixed CVE-2019-12308 -- Made AdminURLFieldWidget validate URL before...
  • 4b3716e [1.11.x] Added stub release notes for security releases.
  • 331d765 [1.11.x] Refs #27807 -- Removed docs for User.username_validator.
  • d13490c [1.11.x] Refs #30331 -- Doc'd that psycopg2 < 2.8 is required.
  • 22c0564 [1.11.x] Fixed #30277 -- Fixed broken links to packaging.python.org.
  • 9530fac [1.11.x] Fixed serializers test crash if PyYAML isn't installed.
  • f8ce3cd [1.11.x] Fixed serializers tests for PyYAML 5.1+.
  • f13bfde [1.11.x] Reverted "Fixed relative paths imports per isort 4.3.5."
  • b9beb6a [1.11.x] Fixed relative paths imports per isort 4.3.5.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

@dependabot-preview dependabot-preview bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code security Pull requests that address a security vulnerability labels Jun 11, 2019
Bumps [django](https://github.com/django/django) from 1.11.10 to 1.11.21. **This update includes security fixes.**
- [Release notes](https://github.com/django/django/releases)
- [Commits](django/django@1.11.10...1.11.21)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/django-1.11.21 branch from 1b46842 to 3242af6 Compare June 17, 2019 17:19
@coveralls
Copy link

Coverage Status

Coverage remained the same at 93.782% when pulling 3242af6 on dependabot/pip/django-1.11.21 into 222ec63 on master.

@dependabot-preview
Copy link
Contributor Author

Superseded by #537.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/django-1.11.21 branch July 4, 2019 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code security Pull requests that address a security vulnerability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant