# CVE-2019-5953: Memory corruption in GNU Wget > Remote attackers can trigger a buffer overflow in GNU Wget to execute arbitrary code or cause denial of service. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 17 May 2019 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2019-5953, CLEANSTART-2026-YM63447, DEBIAN-CVE-2019-5953, DLA-1760-1, DSA-4425-1, GHSA-fhwx-v7qv-pjh3, RHSA-2019:0983, RHSA-2019:1228, RHSA-2019:2979, RHSA-2019:3168, SUSE-SU-2019:0925-1, SUSE-SU-2019:0956-1, UBUNTU-CVE-2019-5953, openSUSE-SU-2019:1236-1 ## What is CVE-2019-5953? CVE-2019-5953 is a critical memory corruption vulnerability in The GNU Projec GNU Wget, published on 17 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2019-5953? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `wget` | Red Hat:enterprise_linux:7::client | All versions | 0:1.14-18.el7_6.1 | | `wget-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.14-18.el7_6.1 | | `wget` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.14-18.el7_6.1 | | `wget-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.14-18.el7_6.1 | | `wget` | Red Hat:enterprise_linux:7::server | All versions | 0:1.14-18.el7_6.1 | | `wget-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.14-18.el7_6.1 | | `wget` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.14-18.el7_6.1 | | `wget-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.14-18.el7_6.1 | | `wget` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.19.5-7.el8_0.1 | | `wget-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.19.5-7.el8_0.1 | | `wget-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.19.5-7.el8_0.1 | | `wget` | Red Hat:rhel_aus:7.4::server | All versions | 0:1.14-15.el7_4.2 | | `wget-debuginfo` | Red Hat:rhel_aus:7.4::server | All versions | 0:1.14-15.el7_4.2 | | `wget` | Red Hat:rhel_e4s:7.4::server | All versions | 0:1.14-15.el7_4.2 | | `wget-debuginfo` | Red Hat:rhel_e4s:7.4::server | All versions | 0:1.14-15.el7_4.2 | | `wget` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.14-16.el7_5.1 | | `wget-debuginfo` | Red Hat:rhel_eus:7.5::computenode | All versions | 0:1.14-16.el7_5.1 | | `wget` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.14-16.el7_5.1 | | `wget-debuginfo` | Red Hat:rhel_eus:7.5::server | All versions | 0:1.14-16.el7_5.1 | | `wget` | Red Hat:rhel_tus:7.4::server | All versions | 0:1.14-15.el7_4.2 | | `wget-debuginfo` | Red Hat:rhel_tus:7.4::server | All versions | 0:1.14-15.el7_4.2 | | `wget` | SUSE:Enterprise Storage 4 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.19.5-3.6.2 | | `wget` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.14-21.10.1 | | `wget` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.14-21.10.1 | | `wget` | SUSE:OpenStack Cloud 7 | All versions | 1.14-21.10.1 | | `wget` | openSUSE:Leap 15.0 | All versions | 1.19.5-lp150.7.1 | Products: Gnu Wget. ## How do I fix CVE-2019-5953? Upgrade to a fixed version. ## Is CVE-2019-5953 being exploited? There is no known exploitation of CVE-2019-5953 in the wild and no public exploit code. ## Other vulnerabilities in The GNU Projec GNU Wget - [CVE-2014-4877](https://insights.sbomify.com/CVE-2014-4877/): Path traversal in n/a (critical 9.3) - [CVE-2024-38428](https://insights.sbomify.com/CVE-2024-38428/): Other in n/a (critical 9.1) - [CVE-2026-58469](https://insights.sbomify.com/CVE-2026-58469/): GNU Wget 1.25.0 Heap Buffer Underread via Metalink URL Parsing (high 8.7) - [CVE-2016-7098](https://insights.sbomify.com/CVE-2016-7098/): Race condition in n/a (high 8.1) - [CVE-2018-20483](https://insights.sbomify.com/CVE-2018-20483/): Information disclosure in n/a (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-5953 and fix it if it is affected. What it is: CVE-2019-5953 is a critical memory corruption vulnerability in The GNU Projec GNU Wget, published on 17 May 2019. 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-2019-5953 in the wild and no public exploit code. Affected product: The GNU Projec GNU Wget. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-2019-5953/ (Markdown: https://insights.sbomify.com/CVE-2019-5953/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5953 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5953 - OSV: https://osv.dev/vulnerability/CVE-2019-5953 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-5953/ Summaries are generated and may contain mistakes; the official description above is the record.