dbcve.org
Airmail 3Application · Bloop

CVE-2018-15668

MEDIUM · 5.3 CVSS v3.0 Published 2018-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The airmail:// URL scheme handler in Bloop Airmail 3 v3.5.9 for macOS accepts a 'send' command that can be invoked by external applications or hyperlinks to automatically transmit emails from an active account. Attachment parameters prefixed with 'attachment_' allow specification of files to attach, including relative file paths, without any user prompt or authorization step.

MitigationUsers should avoid clicking untrusted airmail:// links and consider disabling or restricting the URL handler until an official patch is available from Bloop; organizations may need to implement endpoint controls or browser/content filtering to block malicious airmail:// URL triggers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Airmail 3Application
Affected:= 3.5.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bloop Airmail 3 is installed
    Look for Bloop Airmail 3 in /Applications or use Spotlight to search for 'Airmail'
    Affected if The application is present on the system
  2. Identify the installed version
    Right-click the Airmail app, select 'Get Info', and check the version number under the name, or run: defaults read /Applications/Airmail\ 3.app/Contents/Info CFBundleShortVersionString
    Affected if Version is exactly 3.5.9
  3. Verify airmail:// URL scheme is registered
    Open Terminal and run: defaults read ~/Library/Preferences/com.apple.LaunchServices/com.apple.launchservices.secure.plist | grep -i airmail, or check System Preferences > Security & Privacy > Privacy > Automation for Airmail
    Affected if The airmail:// scheme is listed as an allowed handler
  4. Check for configured email accounts
    Open Airmail 3 and navigate to Settings > Accounts to see if any email accounts are configured and active
    Affected if At least one email account is active in Airmail 3

You are affected if Bloop Airmail 3 version 3.5.9 is installed AND the airmail:// URL scheme is registered AND you have an active email account configured, as this combination allows external programs or links to send emails with attachments without user interaction.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should avoid clicking untrusted airmail:// links and consider disabling or restricting the URL handler until an official patch is available from Bloop; organizations may need to implement endpoint controls or browser/content filtering to block malicious airmail:// URL triggers.

Fix this in Airmail 3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15668 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data