CVSS 3.0
9.8 criticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in gnu glibc. EPSS 3.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2019-1010022 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-1010022?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-1010022?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-1010022 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| GNU C Library glibc | current (At least as of 2018-02-16) |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | glibc | no fix listed | DEBIAN-CVE-2019-1010022 |
| Ubuntu | Pro:16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTS | glibc | no fix listed | UBUNTU-CVE-2019-1010022 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat Product Security does not consider this to be a vulnerability. Also, the upstream project recognizes it as a hardening issue [1], they do not classify it as a security flaw.
Here are some technical notes regarding the issue:
The issue relates to a mitigation bypass in the GNU Libc library's NPTL component, allowing attackers to circumvent stack guard protection via a stack buffer overflow. However, this is considered a post-attack mitigation rather than a direct vulnerability. According to the glibc security process [2], an issue must meet specific criteria for direct exploitation to be deemed a security bug.
In this case, the bypass of stack canary protection occurs by overwriting the stack_guard in the tcbhead_t structure, but only after a successful stack overflow attack. This issue does not directly lead to code execution. Instead, it weakens an additional layer of protection after an attack has already occurred, thus classifying it as a post-attack hardening issue.
In summary, while the issue has security implications, it does not meet the criteria to be classified as a direct security vulnerability.
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=22850#c3
[2] https://sourceware.org/git/?p=glibc.git;a=blob;f=SECURITY.md
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | glibc | Not affected | |
| Red Hat Enterprise Linux 6 | glibc | Not affected | |
| Red Hat Enterprise Linux 7 | glibc | Not affected | |
| Red Hat Enterprise Linux 8 | glibc | Not affected | |
| Red Hat Enterprise Linux 9 | glibc | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-1010022.
| Advisory | Title | Published | Sectors | Affected | Fixed |
|---|---|---|---|---|---|
| ICSA-23-348-10 | Siemens SIMATIC S7-1500 | 2023-12-12 | Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and Facilities | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0), SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0), SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) and 2 more | none listed |
From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).