{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-13386 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-13386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-13386 is a high-severity vulnerability in n/a, published on 27 May 2020. 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-2020-13386 and fix it if it is affected.\n\nWhat it is: CVE-2020-13386 is a high-severity vulnerability in n/a, published on 27 May 2020. 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-2020-13386 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-2020-13386/ (Markdown: https://insights.sbomify.com/CVE-2020-13386/index.md)","id":"CVE-2020-13386","markdown":"https://insights.sbomify.com/CVE-2020-13386/index.md","name":"CVE-2020-13386","record":{"aliases":["GHSA-qxc6-h7rf-c7rf"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SmartDraw desktop app","requires_auth":"low_privilege","summary":"Weak folder permissions allow attackers to plant a malicious binary executed by scheduled tasks, leading to privilege escalation and code execution.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smartdraw_2020","vendor":"smartdraw"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AC:L/AV:L/A:H/C:H/I:H/PR:L/S:C/UI:R","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"In SmartDraw 2020 27.0.0.0, the installer gives inherited write permissions to the Authenticated Users group on the SmartDraw 2020 installation folder. Additionally, when the product is installed, two scheduled tasks are created on the machine, SDMsgUpdate (Local) and SDMsgUpdate (TE). The scheduled tasks run in the context of the user who installed the product. Both scheduled tasks attempt to run the same binary, C:\\SmartDraw 2020\\Messages\\SDNotify.exe. The folder Messages doesn't exist by default and (by extension) neither does SDNotify.exe. Due to the weak folder permissions, these can be created by any user. A malicious actor can therefore create a malicious SDNotify.exe binary, and have it automatically run, whenever the user who installed the product logs on to the machine. The malicious SDNotify.exe could, for example, create a new local administrator account on the machine.","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":"Privilege escalation in n/a","id":"CVE-2020-13386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-13387"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2020-13384"},"products":["n/a"],"published":"2020-05-27","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-04","vendors":["n/a"]},"summary":"Weak folder permissions allow attackers to plant a malicious binary executed by scheduled tasks, leading to privilege escalation and code execution.","url":"https://insights.sbomify.com/CVE-2020-13386/"}