# CVE-2020-14422: Incorrect Calculation and Use of Insufficiently Random Values in Python > A flaw in Python's ipaddress module allows remote attackers to cause denial of service via hash collision attacks on dictionary entries. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Jun 2020 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2020-14422, BIT-libpython-2020-14422, BIT-python-2020-14422, BIT-python-min-2020-14422, CLEANSTART-2026-QW80220, DEBIAN-CVE-2020-14422, DLA-3424-1, GHSA-9gg6-cm3f-wf38, MGASA-2020-0343, PSF-2020-3, SUSE-SU-2020:1822-1, SUSE-SU-2020:1920-1, SUSE-SU-2020:1939-1, SUSE-SU-2020:1940-1, SUSE-SU-2020:2157-1, UBUNTU-CVE-2020-14422, openSUSE-SU-2020:0931-1, openSUSE-SU-2020:0940-1, openSUSE-SU-2020:0989-1, openSUSE-SU-2020:1002-1 ## What is CVE-2020-14422? CVE-2020-14422 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 18 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Lib/ipaddress.py in Python through 3.8.3 improperly computes hash values in the IPv4Interface and IPv6Interface classes, which might allow a remote attacker to cause a denial of service if an application is affected by the performance of a dictionary containing IPv4Interface or IPv6Interface objects, and this attacker can cause many dictionary entries to be created. This is fixed in: v3.5.10, v3.5.10rc1; v3.6.12; v3.7.9; v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1; v3.9.0, v3.9.0b4, v3.9.0b5, v3.9.0rc1, v3.9.0rc2. Weakness: CWE-682 (Incorrect Calculation), CWE-330 (Use of Insufficiently Random Values) ## Which versions are affected by CVE-2020-14422? 3 open source packages ship an affected version, including libpython, python and python-min. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libpython` | Bitnami | From 3.0.0 | 3.5.10, 3.6.12, 3.7.9, 3.8.4 | | `python` | Bitnami | From 3.0.0 | 3.5.10, 3.6.12, 3.7.9, 3.8.4 | | `python-min` | Bitnami | From 3.0.0 | 3.5.10, 3.6.12, 3.7.9, 3.8.4 | | `python-ipaddress` | SUSE:Enterprise Storage 5 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:HPE Helion OpenStack 8 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:HPE Helion OpenStack 8 | All versions | 1.0.18-3.3.1 | | `python-ipaddress` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 1.0.18-3.3.1 | | `python3` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 3.6.10-3.56.1 | | `python-ipaddress` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 1.0.18-3.3.1 | | `python3` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 3.6.10-3.56.1 | | `python3` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 3.6.10-3.56.1 | | `python3` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise Module for Development Tools 15 SP1 | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise Module for Development Tools 15 SP2 | All versions | 3.6.10-3.56.1 | | `python-ipaddress` | SUSE:Linux Enterprise Module for Python 2 15 SP1 | All versions | 1.0.18-3.3.1 | | `python-ipaddress` | SUSE:Linux Enterprise Module for Python 2 15 SP2 | All versions | 1.0.18-3.3.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 1.0.18-3.3.1 | | `python3` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 3.6.10-3.56.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 1.0.18-3.3.1 | | `python3` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 3.6.10-3.56.1 | | `python3-base` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 3.6.10-3.56.1 | | `python-ipaddress` | SUSE:OpenStack Cloud 7 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:OpenStack Cloud 8 | All versions | 1.0.18-3.13.1 | | `python-ipaddress` | SUSE:OpenStack Cloud 8 | All versions | 1.0.18-3.3.1 | | `python-ipaddress` | SUSE:OpenStack Cloud 9 | All versions | 1.0.18-3.13.1 | Products: Fedoraproject Fedora, Opensuse Leap, Oracle Enterprise Manager Ops Center, Python Python. ## How do I fix CVE-2020-14422? Upgrade libpython to a fixed version for your release line: 3.5.10, 3.6.12, 3.7.9 or 3.8.4. ## Is CVE-2020-14422 being exploited? There is no known exploitation of CVE-2020-14422 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-14422 and fix it if it is affected. What it is: CVE-2020-14422 is a medium-severity denial of service vulnerability in Fedoraproject Fedora, published on 18 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-14422 in the wild and no public exploit code. Affected packages and fixed versions: - libpython (Bitnami): affected from 3.0.0; fixed in 3.5.10, 3.6.12, 3.7.9, 3.8.4 - python (Bitnami): affected from 3.0.0; fixed in 3.5.10, 3.6.12, 3.7.9, 3.8.4 - python-min (Bitnami): affected from 3.0.0; fixed in 3.5.10, 3.6.12, 3.7.9, 3.8.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-14422/ (Markdown: https://insights.sbomify.com/CVE-2020-14422/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14422 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14422 - OSV: https://osv.dev/vulnerability/CVE-2020-14422 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-14422/ Summaries are generated and may contain mistakes; the official description above is the record.