# CVE-2018-19519: Memory corruption in n/a > A stack-based buffer over-read in tcpdump allows attackers to cause denial of service or disclose information via crafted packet data. - **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 25 Nov 2018 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2018-19519, ECHO-73f3-1173-c1cb, GHSA-7252-xx9j-xr4g, MGASA-2018-0492, RHSA-2019:3976, RHSA-2020:1604, SUSE-SU-2018:4131-1, SUSE-SU-2018:4149-1, UBUNTU-CVE-2018-19519 ## What is CVE-2018-19519? CVE-2018-19519 is a medium-severity memory corruption vulnerability in Tcpdump Tcpdump, published on 25 Nov 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description In tcpdump 4.9.2, a stack-based buffer over-read exists in the print_prefix function of print-hncp.c via crafted packet data because of missing initialization. Weakness: CWE-909 (Missing Initialization of Resource), CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2018-19519? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tcpdump` | Red Hat:enterprise_linux:7::client | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump` | Red Hat:enterprise_linux:7::computenode | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump` | Red Hat:enterprise_linux:7::server | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump` | Red Hat:enterprise_linux:7::workstation | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 14:4.9.2-4.el7_7.1 | | `tcpdump` | Red Hat:enterprise_linux:8::appstream | All versions | 14:4.9.2-6.el8 | | `tcpdump-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 14:4.9.2-6.el8 | | `tcpdump-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 14:4.9.2-6.el8 | | `tcpdump` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 4.9.2-14.8.1 | | `tcpdump` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 4.9.2-14.8.1 | | `tcpdump` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 4.9.2-3.3.1 | | `tcpdump` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 4.9.2-14.8.1 | | `tcpdump` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 4.9.2-14.8.1 | | `tcpdump` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 4.9.2-14.8.1 | | `tcpdump` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 4.9.2-14.8.1 | Products: Tcpdump Tcpdump. ## How do I fix CVE-2018-19519? Apply the vendor's patch. ## Is CVE-2018-19519 being exploited? There is no known exploitation of CVE-2018-19519 in the wild and no public exploit code. ## Other vulnerabilities in Tcpdump Tcpdump - [CVE-2018-10103](https://insights.sbomify.com/CVE-2018-10103/): tcpdump before 4.9.3 mishandles the printing of SMB data (issue 1 of 2). (critical 9.8) - [CVE-2018-10105](https://insights.sbomify.com/CVE-2018-10105/): Denial of service in n/a (critical 9.8) - [CVE-2017-12893](https://insights.sbomify.com/CVE-2017-12893/): Memory corruption in n/a (critical 9.8) - [CVE-2017-12894](https://insights.sbomify.com/CVE-2017-12894/): Memory corruption in n/a (critical 9.8) - [CVE-2017-12895](https://insights.sbomify.com/CVE-2017-12895/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-19519 and fix it if it is affected. What it is: CVE-2018-19519 is a medium-severity memory corruption vulnerability in Tcpdump Tcpdump, published on 25 Nov 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2018-19519 in the wild and no public exploit code. Affected product: Tcpdump Tcpdump. 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-2018-19519/ (Markdown: https://insights.sbomify.com/CVE-2018-19519/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-19519 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-19519 - OSV: https://osv.dev/vulnerability/CVE-2018-19519 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-19519/ Summaries are generated and may contain mistakes; the official description above is the record.