Page 2 of 33 results (0.004 seconds)

CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 1

mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage. El archivo mfa/FIDO2.py en django-mfa2 versiones anteriores a 2.5.1 y 2.6.x anteriores a 2.6.1, permite un ataque de repetición que podría ser usado para registrar otro dispositivo para un usuario. El desafío de registro del dispositivo no es invalidado después de su uso • https://github.com/mkalioby/django-mfa2/blob/0936ea253354dd95cb127f09d0efa31324caef27/mfa/FIDO2.py#L58 https://github.com/mkalioby/django-mfa2/releases/tag/v2.5.1-release https://github.com/mkalioby/django-mfa2/releases/tag/v2.6.1-release • CWE-294: Authentication Bypass by Capture-replay •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 1

django-s3file is a lightweight file upload input for Django and Amazon S3 . In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the `AWS_LOCATION` setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patch. • https://github.com/codingjoe/django-s3file/commit/68ccd2c621a40eb66fdd6af2be9d5fcc9c373318 https://github.com/codingjoe/django-s3file/security/advisories/GHSA-4w8f-hjm9-xwgf • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0

django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. Users are affected if they have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. • https://github.com/xi/django-mfa3/blob/main/CHANGES.md#050-2022-04-15 https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4 https://security.netapp.com/advisory/ntap-20220609-0003 • CWE-287: Improper Authentication •

CVSS: 9.6EPSS: 0%CPEs: 1EXPL: 1

django-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') django-helpdesk es vulnerable a una Neutralización Inapropiada de Entradas Durante la Generación de Páginas Web ("Cross-site Scripting") • https://github.com/django-helpdesk/django-helpdesk/commit/a22eb0673fe0b7784f99c6b5fd343b64a6700f06 https://huntr.dev/bounties/be7f211d-4bfd-44fd-91e8-682329906fbd • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 0

In Django-wiki, versions 0.0.20 to 0.7.8 are vulnerable to Stored Cross-Site Scripting (XSS) in Notifications Section. An attacker who has access to edit pages can inject JavaScript payload in the title field. When a victim gets a notification regarding the changes made in the application, the payload in the notification panel renders and loads external JavaScript. En Django-wiki, versiones 0.0.20 a 0.7.8, son vulnerables a un ataque de tipo Cross-Site Scripting (XSS) Almacenado en la sección de notificaciones. Un atacante que tenga acceso a las páginas de edición puede inyectar una carga útil de JavaScript en el campo title. • https://github.com/django-wiki/django-wiki/commit/9eaccc7519e4206a4d2f22640882f0737b2da9c5 https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25986 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •