Safety CI > just-work/django-video-transcoding

develop

1 year, 7 months ago

69f51804

Cover metadata with tests

No dependencies with known security vulnerabilities.

develop

1 year, 7 months ago

3b9bfdbd

Add python-3.13 to CI matrix

No dependencies with known security vulnerabilities.

develop

1 year, 7 months ago

bf4af8fd

Mypy cleanup

No dependencies with known security vulnerabilities.

rebased_develop

1 year, 7 months ago

042040d4

Merge remote-tracking branch 'upstream/develop' into develop # Conflicts: # docs/requirements.txt #

No dependencies with known security vulnerabilities.

rebased_develop

1 year, 7 months ago

9ae57512

Missing translations

No dependencies with known security vulnerabilities.

rebased_develop

1 year, 7 months ago

b3530a3b

Fix migrations after rebase

No dependencies with known security vulnerabilities.

master

1 year, 7 months ago

d06e5624

Merge pull request #316 from just-work/update_translations_mr_fixes Update translations mr fixes

No dependencies with known security vulnerabilities.

update_translations_mr_fixes

1 year, 7 months ago

e0943734

Add missing translations properly

No dependencies with known security vulnerabilities.

update_translations_mr_fixes

1 year, 7 months ago

db61f4d7

mypy fixes

No dependencies with known security vulnerabilities.

update_translations_mr_fixes

1 year, 7 months ago

c7feac80

explain crf, gop and force_key_frames

No dependencies with known security vulnerabilities.

update_translations_mr_fixes

1 year, 7 months ago

fc061c2f

Merge pull request #315 from emilkholod/feature/#307-update-translations Update translations

No dependencies with known security vulnerabilities.

master

1 year, 7 months ago

33bbd2c2

Merge pull request #314 from just-work/pyup-update-django-5.0.10-to-5.1.4 Update django from 5.0.10

No dependencies with known security vulnerabilities.

pyup-update-django-5.0.10-to-5.1.4

1 year, 7 months ago

2a3cdab1

Update django from 5.0.10 to 5.1.4

No dependencies with known security vulnerabilities.

master

1 year, 7 months ago

8d55b9f0

Merge pull request #313 from just-work/dependabot/pip/django-5.0.10 Bump django from 5.0.9 to 5.0.1

No dependencies with known security vulnerabilities.

pyup-update-mypy-1.10.1-to-1.14.0

1 year, 7 months ago

ca31e5d0

Update mypy from 1.10.1 to 1.14.0

Django 5.0.9 and Django 5.0.9 have known security vulnerabilities.

Package	Installed	Affected	Info
Django	5.0.9	<4.2.24 , >=5.0a1,<5.1.12 , >=5.2a1,<5.2.6	show Affected versions of the Django package are vulnerable to SQL Injection due to insufficient input sanitization in FilteredRelation column aliases. The FilteredRelation class fails to properly validate or escape column alias names when they are provided through dictionary expansion as keyword arguments to QuerySet.annotate() or QuerySet.alias() methods, allowing malicious SQL code to be injected directly into the generated database queries.
Django	5.0.9	>=5.0a1,<5.0.14 , >=5.1a1,<5.1.8	show An issue was discovered in Django 5.1 before 5.1.8 and 5.0 before 5.0.14. The NFKC normalization is slow on Windows. As a consequence, django.contrib.auth.views.LoginView, django.contrib.auth.views.LogoutView, and django.views.i18n.set_language are subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters.
Django	5.0.9	>=4.2a1,<4.2.20 , >=5.0a1,<5.0.13 , >=5.1a1,<5.1.7	show Affected versions of Django are vulnerable to a potential denial-of-service in django.utils.text.wrap(). The django.utils.text.wrap() and wordwrap template filter were subject to a potential denial-of-service attack when used with very long strings.
Django	5.0.9	<4.2.17 , >=5.0a1,<5.0.10 , >=5.1a1,<5.1.4	show Django affected versions are vulnerable to a potential SQL injection in the HasKey(lhs, rhs) lookup on Oracle databases. The vulnerability arises when untrusted data is directly used as the lhs value in the django.db.models.fields.json.HasKey lookup. However, applications using the jsonfield.has_key lookup with the __ syntax remain unaffected by this issue.
Django	5.0.9	>=5.2,<5.2.2 , >=5.0a1,<5.1.10 , <4.2.22	show An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems.
Django	5.0.9	<4.2.17 , >=5.0a1,<5.0.10 , >=5.1a1,<5.1.4	show Affected versions of Django are vulnerable to a potential denial-of-service (DoS) attack in the `django.utils.html.strip_tags()` method. The vulnerability occurs when the `strip_tags()` method or the `striptags` template filter processes inputs containing large sequences of nested, incomplete HTML entities.
Django	5.0.9	>=5.1a1,<5.1.5 , >=5.0a1,<5.0.11 , >=4.2a1,<4.2.18	show Affected versions of Django are vulnerable to a potential denial-of-service attack due to improper IPv6 validation. The lack of upper limit enforcement for input strings in clean_ipv6_address, is_valid_ipv6_address, and the django.forms.GenericIPAddressField form field allowed attackers to exploit overly long inputs, causing resource exhaustion. The vulnerability is addressed by defining a max_length of 39 characters for affected form fields. The django.db.models.GenericIPAddressField model field was not impacted. Users should upgrade promptly.
Django	5.0.9	<4.2.24 , >=5.0a1,<5.1.12 , >=5.2a1,<5.2.6	show Affected versions of the Django package are vulnerable to SQL Injection due to insufficient input sanitization in FilteredRelation column aliases. The FilteredRelation class fails to properly validate or escape column alias names when they are provided through dictionary expansion as keyword arguments to QuerySet.annotate() or QuerySet.alias() methods, allowing malicious SQL code to be injected directly into the generated database queries.
Django	5.0.9	>=5.0a1,<5.0.14 , >=5.1a1,<5.1.8	show An issue was discovered in Django 5.1 before 5.1.8 and 5.0 before 5.0.14. The NFKC normalization is slow on Windows. As a consequence, django.contrib.auth.views.LoginView, django.contrib.auth.views.LogoutView, and django.views.i18n.set_language are subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters.
Django	5.0.9	>=4.2a1,<4.2.20 , >=5.0a1,<5.0.13 , >=5.1a1,<5.1.7	show Affected versions of Django are vulnerable to a potential denial-of-service in django.utils.text.wrap(). The django.utils.text.wrap() and wordwrap template filter were subject to a potential denial-of-service attack when used with very long strings.
Django	5.0.9	<4.2.17 , >=5.0a1,<5.0.10 , >=5.1a1,<5.1.4	show Django affected versions are vulnerable to a potential SQL injection in the HasKey(lhs, rhs) lookup on Oracle databases. The vulnerability arises when untrusted data is directly used as the lhs value in the django.db.models.fields.json.HasKey lookup. However, applications using the jsonfield.has_key lookup with the __ syntax remain unaffected by this issue.
Django	5.0.9	>=5.2,<5.2.2 , >=5.0a1,<5.1.10 , <4.2.22	show An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems.
Django	5.0.9	<4.2.17 , >=5.0a1,<5.0.10 , >=5.1a1,<5.1.4	show Affected versions of Django are vulnerable to a potential denial-of-service (DoS) attack in the `django.utils.html.strip_tags()` method. The vulnerability occurs when the `strip_tags()` method or the `striptags` template filter processes inputs containing large sequences of nested, incomplete HTML entities.
Django	5.0.9	>=5.1a1,<5.1.5 , >=5.0a1,<5.0.11 , >=4.2a1,<4.2.18	show Affected versions of Django are vulnerable to a potential denial-of-service attack due to improper IPv6 validation. The lack of upper limit enforcement for input strings in clean_ipv6_address, is_valid_ipv6_address, and the django.forms.GenericIPAddressField form field allowed attackers to exploit overly long inputs, causing resource exhaustion. The vulnerability is addressed by defining a max_length of 39 characters for affected form fields. The django.db.models.GenericIPAddressField model field was not impacted. Users should upgrade promptly.