Workflow

PyPi: Django-Secured-Fields

CVE-2022-34265

Transitive

Safety vulnerability ID: 52688

This vulnerability was reviewed by experts

The information on this page was manually curated by our Cybersecurity Intelligence Team.

Created at Jul 04, 2022 Updated at Nov 29, 2024
Scan your Python projects for vulnerabilities →

Advisory

Django-secured-fields 0.4.1 updates its dependency 'Django' to v4.0.6 to include security fixes.

Affected package

django-secured-fields

Latest version: 0.4.4

None

Affected versions

Fixed versions

Vulnerability changelog

What's Changed
* Bump django from 4.0.2 to 4.0.4 by dependabot in https://github.com/C0D1UM/django-secured-fields/pull/23
* Bump django from 4.0.4 to 4.0.6 by dependabot in https://github.com/C0D1UM/django-secured-fields/pull/24


**Full Changelog**: https://github.com/C0D1UM/django-secured-fields/compare/v0.4.0...v0.4.1

Resources

Use this package?

Scan your Python project for dependency vulnerabilities in two minutes

Scan your application

Severity Details

CVSS Base Score

CRITICAL 9.8

CVSS v3 Details

CRITICAL 9.8
Attack Vector (AV)
NETWORK
Attack Complexity (AC)
LOW
Privileges Required (PR)
NONE
User Interaction (UI)
NONE
Scope (S)
UNCHANGED
Confidentiality Impact (C)
HIGH
Integrity Impact (I)
HIGH
Availability Availability (A)
HIGH

CVSS v2 Details

HIGH 7.5
Access Vector (AV)
NETWORK
Access Complexity (AC)
LOW
Authentication (Au)
NONE
Confidentiality Impact (C)
PARTIAL
Integrity Impact (I)
PARTIAL
Availability Impact (A)
PARTIAL