dbcve.org
Evolution Data ServerApplication · Gnome

CVE-2009-0582

MEDIUM · 5.8 CVSS v2.0 Published 2009-03-14
Fix available
A fix is available. Upgrade to after 2.24.5 or later.
See remediation →
67/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 ntlm_challenge function in the NTLM SASL authentication mechanism in camel/camel-sasl-ntlm.c in Camel in Evolution Data Server (aka evolution-data-server) 2.24.5 and earlier, and 2.25.92 and earlier 2.25.x versions, does not validate whether a certain length value is consistent with the amount of data in a challenge packet, which allows remote mail servers to read information from the process memory of a client, or cause a denial of service (client crash), via an NTLM authentication type 2 packet with a length value that exceeds the amount of packet data.

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 NTLM SASL authentication mechanism in Evolution Data Server's Camel library fails to validate that length values in NTLM Type 2 challenge packets match the actual data available. This allows a malicious mail server to send packets with oversized length fields, causing the client to read beyond buffer boundaries (information disclosure from process memory) or crash.

MitigationUpgrade to Evolution Data Server version 2.24.6 or later, or 2.25.93 or later for the 2.25.x branch. If patching, add bounds checking in ntlm_challenge() to verify length values do not exceed available packet data before processing.

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
Evolution Data ServerApplication
Affected:<= 2.24.5= 2.25.92

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

AV:N/AC:M/Au:N/C:P/I:N/A:P

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 Evolution Data Server installation
    Run 'rpm -q evolution-data-server' (RHEL/Fedora) or 'dpkg -l libevolution' (Debian/Ubuntu) to find the installed package version. On other systems, check for the 'camel' library version via 'camel --version' or inspect the shared library file in /usr/lib/
    Affected if The installed version is 2.24.5 or earlier, or exactly 2.25.92
  2. Confirm Camel library presence
    Locate the Camel library by searching for 'libcamel' - typically found in /usr/lib/ as libcamel.so or libcamel-1.2.so. Use 'ldd' on the evolution-data-server binary or check package contents to verify Camel is installed as part of Evolution Data Server
    Affected if Camel library version cannot be determined or is not installed, but Evolution Data Server version indicates vulnerability
  3. Identify NTLM-authenticated accounts
    Review mail account configurations in Evolution (or any application using Camel) for accounts using NTLM authentication. Check /home/*/.config/evolution/mail/local.xml or Evolution's account settings UI for authentication method 'NTLM'
    Affected if Any mail account is configured to use NTLM SASL authentication, making the client vulnerable to malformed packets from the mail server
  4. Check for vulnerable service exposure
    Identify processes using Camel for mail: run 'ps aux | grep evolution' or check for any daemon using libevolution (such as evolution-exchange, evolution-alarm-notify, or applications connecting to Exchange/IMAP servers with NTLM)
    Affected if Evolution or an Evolution-based mail client is running and actively connecting to mail servers

If Evolution Data Server version is 2.24.5 or earlier, or exactly 2.25.92, AND NTLM authentication is enabled on any configured mail account, the environment is affected by this vulnerability.

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
Upgrade available Upgrade to a release after 2.24.5
Interim mitigation

Upgrade to Evolution Data Server version 2.24.6 or later, or 2.25.93 or later for the 2.25.x branch. If patching, add bounds checking in ntlm_challenge() to verify length values do not exceed available packet data before processing.

Fix this in Evolution Data Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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