CVE-2023-32290
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 · uneditedThe myMail app through 14.30 for iOS sends cleartext credentials in a situation where STARTTLS is expected by a server.
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 confidenceThe myMail iOS app through version 14.30 transmits user credentials in cleartext instead of waiting for or properly negotiating TLS encryption via STARTTLS. When connecting to email servers that expect a STARTTLS upgrade before accepting credentials, the app sends authentication data unencrypted, allowing network eavesdroppers to intercept credentials.
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<= 14.30CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed myMail versionOn iOS, go to Settings > General > iPhone Storage, locate myMail in the app list, and view the version number. Alternatively, open the App Store, go to myMail app page, and check the version field.Affected if The version is 14.30 or lower (any version up to and including 14.30).
-
Identify email server configuration in myMailOpen myMail app, go to Settings (gear icon), tap on your email account, and view the incoming mail server settings. Note the port number (typically 587 for STARTTLS, 465 for implicit TLS) and server address.Affected if The account is configured to use port 587 or another port that expects STARTTLS upgrade before accepting credentials.
-
Determine if email server expects STARTTLSContact your email provider or check their documentation to confirm whether their SMTP/IMAP server expects STARTTLS negotiation before accepting authentication. Port 587 with STARTTLS is common; port 465 uses implicit TLS from the start.Affected if The email server expects a STARTTLS upgrade before accepting credentials and you are using myMail version 14.30 or lower.
You are affected if you have myMail iOS app version 14.30 or lower and use it to connect to email servers that require STARTTLS negotiation before accepting credentials.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate myMail iOS app to version 14.31 or later, which contains the fix for proper STARTTLS negotiation. Alternatively, use an alternative email client that correctly implements STARTTLS or uses implicit TLS from connection start.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-32290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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