Workflow

PyPi: Django-Secured-Fields

CVE-2022-21699

Transitive

Safety vulnerability ID: 45843

This vulnerability was reviewed by experts

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

Created at Jan 19, 2022 Updated at Nov 29, 2024
Scan your Python projects for vulnerabilities →

Advisory

Django-secured-fields 0.3.1 updates its dependency 'ipython' to v7.31.1 to include a security fix.

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

HIGH 8.8

CVSS v3 Details

HIGH 8.8
Attack Vector (AV)
LOCAL
Attack Complexity (AC)
LOW
Privileges Required (PR)
LOW
User Interaction (UI)
NONE
Scope (S)
CHANGED
Confidentiality Impact (C)
HIGH
Integrity Impact (I)
HIGH
Availability Availability (A)
HIGH

CVSS v2 Details

MEDIUM 4.6
Access Vector (AV)
LOCAL
Access Complexity (AC)
LOW
Authentication (Au)
NONE
Confidentiality Impact (C)
PARTIAL
Integrity Impact (I)
PARTIAL
Availability Impact (A)
PARTIAL