# CVE-2016-10739: Other in n/a > The glibc getaddrinfo function incorrectly parses IPv4 addresses with trailing whitespace, potentially allowing attackers to bypass input validation checks. - **Severity:** Medium 5.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Jan 2019 - **Updated:** 14 Oct 2026 - **Also known as:** DEBIAN-CVE-2016-10739, GHSA-8r2c-r3r4-4hcp, RHSA-2019:2118, RHSA-2019:3513, SUSE-SU-2019:0903-1, SUSE-SU-2023:0015-1, UBUNTU-CVE-2016-10739, openSUSE-SU-2019:1250-1 ## What is CVE-2016-10739? CVE-2016-10739 is a medium-severity vulnerability in Gnu Glibc, published on 21 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrectly assume that it had parsed a valid string, without the possibility of embedded HTTP headers or other potentially dangerous substrings. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2016-10739? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `glibc` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-common` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-headers` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-static` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc-utils` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `nscd` | Red Hat:enterprise_linux:7::client | All versions | 0:2.17-292.el7 | | `glibc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-common` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-headers` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc-utils` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `nscd` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.17-292.el7 | | `glibc` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-common` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-headers` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-static` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc-utils` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `nscd` | Red Hat:enterprise_linux:7::server | All versions | 0:2.17-292.el7 | | `glibc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-headers` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-static` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `glibc-utils` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `nscd` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.17-292.el7 | | `compat-libpthread-nonshared` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.28-72.el8 | | `glibc-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.28-72.el8 | | `glibc-debuginfo-common` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.28-72.el8 | | `glibc-utils` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.28-72.el8 | Products: Gnu Glibc, Opensuse Leap. ## How do I fix CVE-2016-10739? Apply the vendor's patch. ## Is CVE-2016-10739 being exploited? There is no known exploitation of CVE-2016-10739 in the wild and no public exploit code. ## Other vulnerabilities in Gnu Glibc - [CVE-2026-5450](https://insights.sbomify.com/CVE-2026-5450/): scanf %mc off-by-one heap buffer overflow (critical 9.8) - [CVE-2023-25139](https://insights.sbomify.com/CVE-2023-25139/): Memory corruption in n/a (critical 9.8) - [CVE-1999-0199](https://insights.sbomify.com/CVE-1999-0199/): Other in n/a (critical 9.8) - [CVE-2019-1010022](https://insights.sbomify.com/CVE-2019-1010022/): Security feature bypass in glibc (critical 9.8) - [CVE-2005-3590](https://insights.sbomify.com/CVE-2005-3590/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-10739 and fix it if it is affected. What it is: CVE-2016-10739 is a medium-severity vulnerability in Gnu Glibc, published on 21 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-10739 in the wild and no public exploit code. Affected product: Gnu Glibc. 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-2016-10739/ (Markdown: https://insights.sbomify.com/CVE-2016-10739/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-10739 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-10739 - OSV: https://osv.dev/vulnerability/CVE-2016-10739 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-10739/ Summaries are generated and may contain mistakes; the official description above is the record.