dbcve.org
Mac Os XOperating system · Apple

CVE-2002-2326

MEDIUM · 5.0 CVSS v2.0 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
The default configuration of Mail.app in Mac OS X 10.0 through 10.0.4 and 10.1 through 10.1.5 sends iDisk authentication credentials in cleartext when connecting to Mac.com, which could allow remote attackers to obtain passwords by sniffing network traffic.

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

Mail.app in Mac OS X 10.0 through 10.0.4 and 10.1 through 10.1.5 transmits iDisk authentication credentials in cleartext when connecting to Mac.com servers, enabling attackers on the same network to intercept passwords via packet sniffing.

MitigationConfigure Mail.app to use SSL/TLS encryption for authentication, or migrate to a modern email service with secure authentication protocols, as Mac.com services have been discontinued.

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
Mac Os XOperating system
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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. Identify Mac OS X version
    Click Apple menu > About This Mac to view the OS version number
    Affected if The version shown is 10.0.x (through 10.0.4) or 10.1.x (through 10.1.5)
  2. Check if Mail.app uses a Mac.com account
    Open Mail.app, go to Mail > Preferences > Accounts, and examine the account settings for a Mac.com, iDisk, or .me email address
    Affected if An account configured with @mac.com or @me.com address exists and is set to connect to Apple's servers
  3. Verify authentication settings for Mac.com accounts
    In Mail preferences, select the Mac.com account and check the 'Outgoing Mail Server' settings for the account
    Affected if Authentication is enabled but SSL/TLS encryption is not selected or configured for the connection

A user is affected if they are running Mac OS X 10.0.x or 10.1.x with Mail.app configured to use a Mac.com account without SSL/TLS encryption enabled for authentication.

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

Configure Mail.app to use SSL/TLS encryption for authentication, or migrate to a modern email service with secure authentication protocols, as Mac.com services have been discontinued.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2326 — 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-2002-2326 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