Workflow

PyPi: Django-Secured-Fields

CVE-2022-22818

Transitive

Safety vulnerability ID: 45850

This vulnerability was reviewed by experts

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

Created at Feb 03, 2022 Updated at Nov 29, 2024
Scan your Python projects for vulnerabilities →

Advisory

Django-secured-fields 0.3.1 updates its dependency 'django' to v4.0.2 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 ipython from 7.31.0 to 7.31.1 by dependabot in https://github.com/C0D1UM/django-secured-fields/pull/15
* Bump django from 4.0.1 to 4.0.2 by dependabot in https://github.com/C0D1UM/django-secured-fields/pull/16

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

Resources

Use this package?

Scan your Python project for dependency vulnerabilities in two minutes

Scan your application

Severity Details

CVSS Base Score

MEDIUM 6.1

CVSS v3 Details

MEDIUM 6.1
Attack Vector (AV)
NETWORK
Attack Complexity (AC)
LOW
Privileges Required (PR)
NONE
User Interaction (UI)
REQUIRED
Scope (S)
CHANGED
Confidentiality Impact (C)
LOW
Integrity Impact (I)
LOW
Availability Availability (A)
NONE

CVSS v2 Details

MEDIUM 4.3
Access Vector (AV)
NETWORK
Access Complexity (AC)
MEDIUM
Authentication (Au)
NONE
Confidentiality Impact (C)
NONE
Integrity Impact (I)
PARTIAL
Availability Impact (A)
NONE