{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17051 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17051 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17051 is a high-severity vulnerability in n/a, published on 30 Sep 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-2019-17051 and fix it if it is affected.\n\nWhat it is: CVE-2019-17051 is a high-severity vulnerability in n/a, published on 30 Sep 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-2019-17051 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-2019-17051/ (Markdown: https://insights.sbomify.com/CVE-2019-17051/index.md)","id":"CVE-2019-17051","markdown":"https://insights.sbomify.com/CVE-2019-17051/index.md","name":"CVE-2019-17051","record":{"aliases":["GHSA-rgvr-8fj2-9g73"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Evernote macOS client","requires_auth":"none","summary":"Attackers can execute arbitrary code on macOS by bypassing the quarantine attribute via crafted attachments in Evernote.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"evernote","vendor":"evernote"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Evernote before 7.13 GA on macOS allows code execution because the com.apple.quarantine attribute is not used for attachment files, as demonstrated by a one-click attack involving a drag-and-drop operation on a crafted Terminal file.","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":"Security feature bypass in n/a","id":"CVE-2019-17051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-17052"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2019-17050"},"products":["n/a"],"published":"2019-09-30","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-50643","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-17759","kev_date_added":null,"published":"2021-06-24"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2019-10038","kev_date_added":null,"published":"2019-05-31"},{"cvss_score":7.8,"headline":"Privilege escalation in Evernote for Windows","id":"CVE-2016-4900","kev_date_added":null,"published":"2017-05-22"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2018-20058","kev_date_added":null,"published":"2018-12-11"},{"cvss_score":7.1,"headline":"Auth bypass in n/a","id":"CVE-2013-5116","kev_date_added":null,"published":"2020-01-31"}],"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 execute arbitrary code on macOS by bypassing the quarantine attribute via crafted attachments in Evernote.","url":"https://insights.sbomify.com/CVE-2019-17051/"}