{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18269 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-18269 is a critical memory corruption vulnerability in Gnu Glibc, published on 18 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-18269 and fix it if it is affected.\n\nWhat it is: CVE-2017-18269 is a critical memory corruption vulnerability in Gnu Glibc, published on 18 May 2018. 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-2017-18269 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-2017-18269/ (Markdown: https://insights.sbomify.com/CVE-2017-18269/index.md)","id":"CVE-2017-18269","markdown":"https://insights.sbomify.com/CVE-2017-18269/index.md","name":"CVE-2017-18269","record":{"aliases":["DEBIAN-CVE-2017-18269","GHSA-r6cp-c5hh-vmv8","UBUNTU-CVE-2017-18269"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GNU C Library","requires_auth":"none","summary":"A flaw in glibc's SSE2 memmove implementation causes data corruption, potentially leading to information disclosure, denial of service, or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"glibc","vendor":"gnu"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An SSE2-optimized memmove implementation for i386 in sysdeps/i386/i686/multiarch/memcpy-sse2-unaligned.S in the GNU C Library (aka glibc or libc6) 2.21 through 2.27 does not correctly perform the overlapping memory check if the source memory range spans the middle of the address space, resulting in corrupt data being produced by the copy operation. This may disclose information to context-dependent attackers, or result in a denial of service, or, possibly, code execution.","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":"Memory corruption in n/a","id":"CVE-2017-18269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"gnu:glibc","products":["gnu:glibc"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":6,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2017-18270"},"packages":[],"prev":{"headline":"Weak cryptography in IntelligenceCenter","id":"CVE-2017-18268"},"products":["n/a"],"published":"2018-05-18","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":"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":"2024-08-05","vendors":["n/a"]},"summary":"A flaw in glibc's SSE2 memmove implementation causes data corruption, potentially leading to information disclosure, denial of service, or code execution.","url":"https://insights.sbomify.com/CVE-2017-18269/"}