{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1010024 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2019-1010024 is a medium-severity vulnerability in Gnu Glibc, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-1010024 and fix it if it is affected.\n\nWhat it is: CVE-2019-1010024 is a medium-severity vulnerability in Gnu Glibc, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-1010024 in the wild and no public exploit code.\n\nAffected product: Gnu Glibc. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-1010024/ (Markdown: https://insights.sbomify.com/CVE-2019-1010024/index.md)","id":"CVE-2019-1010024","markdown":"https://insights.sbomify.com/CVE-2019-1010024/index.md","name":"CVE-2019-1010024","record":{"aliases":["DEBIAN-CVE-2019-1010024","GHSA-3q29-89cr-qgvj","MINI-85gf-7hp6-cjv2","MINI-r5x8-hhfx-4867","MINI-wqg3-cgwm-768p","UBUNTU-CVE-2019-1010024"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GNU C Library","requires_auth":"none","summary":"Attackers can bypass ASLR protections in glibc by exploiting thread stack and heap caches, though upstream considers this a non-security bug.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dwf","cpe":[{"product":"glibc","vendor":"gnu"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate \"this is being treated as a non-security bug and no real threat.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Security feature bypass in glibc","id":"CVE-2019-1010024","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"gnu:glibc","products":["gnu:glibc"],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in glibc","id":"CVE-2019-1010025"},"packages":[],"prev":{"headline":"Code injection in glibc","id":"CVE-2019-1010023"},"products":["glibc"],"published":"2019-07-15","related":[{"cvss_score":9.8,"headline":"scanf %mc off-by-one heap buffer overflow","id":"CVE-2026-5450","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-25139","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-1999-0199","kev_date_added":null,"published":"2020-10-06"},{"cvss_score":9.8,"headline":"Security feature bypass in glibc","id":"CVE-2019-1010022","kev_date_added":null,"published":"2019-07-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2005-3590","kev_date_added":null,"published":"2019-04-10"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18269","kev_date_added":null,"published":"2018-05-18"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2018-11236","kev_date_added":null,"published":"2018-05-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-14","vendors":["GNU Libc"]},"summary":"Attackers can bypass ASLR protections in glibc by exploiting thread stack and heap caches, though upstream considers this a non-security bug.","url":"https://insights.sbomify.com/CVE-2019-1010024/"}