{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-5392 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-5392 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-5392 is a high-severity vulnerability in mingw-w64, published on 14 Aug 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-2018-5392 and fix it if it is affected.\n\nWhat it is: CVE-2018-5392 is a high-severity vulnerability in mingw-w64, published on 14 Aug 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-2018-5392 in the wild and no public exploit code.\n\nAffected product: mingw-w64. 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-2018-5392/ (Markdown: https://insights.sbomify.com/CVE-2018-5392/index.md)","id":"CVE-2018-5392","markdown":"https://insights.sbomify.com/CVE-2018-5392/index.md","name":"CVE-2018-5392","record":{"aliases":["DEBIAN-CVE-2018-5392","ECHO-3985-4d70-6d87","GHSA-x4v8-qgp4-6739","UBUNTU-CVE-2018-5392"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MinGW-w64 compiler","requires_auth":"none","summary":"MinGW-w64 generates executables claiming ASLR compatibility but lacking relocation tables, allowing attackers to bypass ASLR mitigations for easier exploitation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"mingw-w64","vendor":"mingw"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-824","name":"Access of Uninitialized Pointer"}],"description":"mingw-w64 version 5.0.4 by default produces executables that opt in to ASLR, but are not compatible with ASLR. ASLR is an exploit mitigation technique used by modern Windows platforms. For ASLR to function, Windows executables must contain a relocations table. Despite containing the \"Dynamic base\" PE header, which indicates ASLR compatibility, Windows executables produced by mingw-w64 have the relocations table stripped from them by default. This means that executables produced by mingw-w64 are vulnerable to return-oriented programming (ROP) attacks. Windows executables generated by mingw-w64 claim to be ASLR compatible, but are not. Vulnerabilities in such executables are more easily exploitable as a result.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"mingw-w64 version 5.0.4 by default produces executables that opt in to ASLR, but are not compatible with ASLR","id":"CVE-2018-5392","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"TP-Link EAP Controller versions 2.5.3 and earlier lack RMI authentication","id":"CVE-2018-5393"},"packages":[],"prev":{"headline":"Denial of service in Kernel","id":"CVE-2018-5391"},"products":["mingw-w64"],"published":"2018-08-14","related":[],"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":["mingw"]},"summary":"MinGW-w64 generates executables claiming ASLR compatibility but lacking relocation tables, allowing attackers to bypass ASLR mitigations for easier exploitation.","url":"https://insights.sbomify.com/CVE-2018-5392/"}