{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18253 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18253 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18253 is a high-severity vulnerability in n/a, published on 15 Mar 2019. 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-18253 and fix it if it is affected.\n\nWhat it is: CVE-2018-18253 is a high-severity vulnerability in n/a, published on 15 Mar 2019. 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-18253 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-18253/ (Markdown: https://insights.sbomify.com/CVE-2018-18253/index.md)","id":"CVE-2018-18253","markdown":"https://insights.sbomify.com/CVE-2018-18253/index.md","name":"CVE-2018-18253","record":{"aliases":["GHSA-c433-q7cj-fw94"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CapMon Access Manager","requires_auth":"low_privilege","summary":"A race condition in CapMon Access Manager allows attackers to retain administrator privileges if a command crashes, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"access_manager","vendor":"capmon"}],"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-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"An issue was discovered in CapMon Access Manager 5.4.1.1005. CALRunElevated.exe attempts to enforce access control by adding an unprivileged user to the local Administrators group for a very short time to execute a single command. However, the user is left in that group if the command crashes, and there is also a race condition in all cases.","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-18253","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":"Missing authorization in n/a","id":"CVE-2018-18254"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2018-18252"},"products":["n/a"],"published":"2019-03-15","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-18252","kev_date_added":null,"published":"2019-03-15"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2018-18254","kev_date_added":null,"published":"2019-03-15"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-18255","kev_date_added":null,"published":"2019-03-15"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-18256","kev_date_added":null,"published":"2019-03-15"}],"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 race condition in CapMon Access Manager allows attackers to retain administrator privileges if a command crashes, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2018-18253/"}