{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19113 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19113 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19113 is a high-severity vulnerability in n/a, published on 1 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-19113 and fix it if it is affected.\n\nWhat it is: CVE-2018-19113 is a high-severity vulnerability in n/a, published on 1 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-19113 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-19113/ (Markdown: https://insights.sbomify.com/CVE-2018-19113/index.md)","id":"CVE-2018-19113","markdown":"https://insights.sbomify.com/CVE-2018-19113/index.md","name":"CVE-2018-19113","record":{"aliases":["GHSA-33r8-p23p-5pwc"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Outlook add-in","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by replacing the executable due to insecure file permissions in the Pronestor Health Monitoring Outlook add-in.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pronestor_health_monitoring","vendor":"pronestor"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"The Pronestor PNHM (aka Health Monitoring or HealthMonitor) add-in before 8.1.13.0 for Outlook has \"BUILTIN\\Users:(I)(F)\" permissions for the \"%PROGRAMFILES(X86)%\\proNestor\\Outlook add-in for Pronestor\\PronestorHealthMonitor.exe\" file, which allows local users to gain privileges via a Trojan horse PronestorHealthMonitor.exe file.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-06-13","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-06-13","kind":"exploitdb","ref":"46988","stars":null,"title":"Pronestor Health Monitoring \u003c 8.1.11.0 - Privilege Escalation"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2018-19113","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2018-19114"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-19111"},"products":["n/a"],"published":"2019-04-01","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can escalate privileges by replacing the executable due to insecure file permissions in the Pronestor Health Monitoring Outlook add-in.","url":"https://insights.sbomify.com/CVE-2018-19113/"}