{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-5731 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-5731 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-5731 is a high-severity vulnerability in n/a, published on 22 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-5731 and fix it if it is affected.\n\nWhat it is: CVE-2018-5731 is a high-severity vulnerability in n/a, published on 22 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-5731 in the wild and no public exploit code.\n\nAffected product: n/a. 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-5731/ (Markdown: https://insights.sbomify.com/CVE-2018-5731/index.md)","id":"CVE-2018-5731","markdown":"https://insights.sbomify.com/CVE-2018-5731/index.md","name":"CVE-2018-5731","record":{"aliases":["GHSA-jr9q-cm32-5462"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Heimdal PRO antivirus","requires_auth":"low_privilege","summary":"Attackers can achieve code execution by exploiting a race condition in the scanning feature of Heimdal PRO antivirus software.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"heimdal","vendor":"heimdalsecurity"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in Heimdal PRO 2.2.190. As part of the scanning feature, a process called md.hs writes an executable called CS1.tmp to C:\\windows\\TEMP. Afterwards the executable is run. It is possible for an attacker to create the file first, let md.hs overwrite it, and then rewrite the file in the window between md.hs closing the file and executing it. This can be exploited via opportunistic locks and a high priority thread. The vulnerability is triggered when a scan starts. NOTE: any affected Heimdal products are completely unrelated to the Heimdal vendor of a Kerberos 5 product on the h5l.org web site.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Race condition in n/a","id":"CVE-2018-5731","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"A specially constructed response from a malicious server can cause a buffer overflow in dhclient","id":"CVE-2018-5732"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-5730"},"products":["n/a"],"published":"2018-03-22","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-5349","kev_date_added":null,"published":"2018-03-22"}],"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":"Attackers can achieve code execution by exploiting a race condition in the scanning feature of Heimdal PRO antivirus software.","url":"https://insights.sbomify.com/CVE-2018-5731/"}