{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15668 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15668 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15668 is a medium-severity vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-15668 and fix it if it is affected.\n\nWhat it is: CVE-2018-15668 is a medium-severity vulnerability in n/a, published on 21 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-15668 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-15668/ (Markdown: https://insights.sbomify.com/CVE-2018-15668/index.md)","id":"CVE-2018-15668","markdown":"https://insights.sbomify.com/CVE-2018-15668/index.md","name":"CVE-2018-15668","record":{"aliases":["GHSA-g4h8-wjhq-75pg"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read","other"],"network_reachable":"yes","non_default_config":false,"product_category":"macOS email client","requires_auth":"none","summary":"Attackers can exploit the URL scheme to silently send emails with arbitrary file attachments from a user's account, leading to data leakage.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"airmail_3","vendor":"bloop"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in Bloop Airmail 3 3.5.9 for macOS. The \"send\" command in the airmail:// URL scheme allows an external application to send arbitrary emails from an active account. URL parameters for the \"send\" command with the \"attachment_\" prefix designate attachment parameters. If the value of an attachment parameter corresponds to an accessible file path, the file is attached to the outbound message. In addition, relative file paths are acceptable attachment parameter values. The handler can be invoked using any method that invokes the URL handler such as a hyperlink in an email. The user is not prompted when the handler processes the \"send\" command, thus leading to automatic transmission of an email with designated attachments from the target account to a target address.","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":"Information disclosure in n/a","id":"CVE-2018-15668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2018-15669"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2018-15667"},"products":["n/a"],"published":"2018-08-21","related":[{"cvss_score":5.3,"headline":"Security feature bypass in n/a","id":"CVE-2018-15669","kev_date_added":null,"published":"2018-08-21"}],"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 exploit the URL scheme to silently send emails with arbitrary file attachments from a user's account, leading to data leakage.","url":"https://insights.sbomify.com/CVE-2018-15668/"}