Skip to content
Noroxi
CVE-2009-0582· NVD / CVE Program· CNA redhat

The ntlm_challenge function in the NTLM SASL authentication mechanism in camel/camel-sasl-ntlm.c in Camel in Evolution Data Server (aka evol

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.

MediumCVSS 5.8 · v2.0—No exploit Fix available
Published
Mar 14, 2009
Updated
Jun 16, 2026
EPSS
2.3% · 82th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
23 / 40 · 5.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.3%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
gnomeevolution-data-server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnome evolution-data-serverup to 2.24.5 inclusive
  • gnome evolution-data-server2.25.92

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12evolution-data-serverbefore 2.26.1.1-12.26.1.1-1
Debian:4.0evolution-data-serverbefore 1.6.3-5etch21.6.3-5etch2
Debian:5.0evolution-data-serverbefore 2.22.3-1.1+lenny12.22.3-1.1+lenny1
Red Hat:enterprise_linux:3::asevolutionbefore 0:1.4.5-25.el30:1.4.5-25.el3
Red Hat:enterprise_linux:3::asevolution-debuginfobefore 0:1.4.5-25.el30:1.4.5-25.el3
Red Hat:enterprise_linux:3::asevolution-develbefore 0:1.4.5-25.el30:1.4.5-25.el3
Red Hat:enterprise_linux:4::asevolutionbefore 0:2.0.2-41.el4_7.20:2.0.2-41.el4_7.2
Red Hat:enterprise_linux:4::asevolution-data-serverbefore 0:1.0.2-14.el4_7.10:1.0.2-14.el4_7.1
Red Hat:enterprise_linux:4::asevolution-data-server-debuginfobefore 0:1.0.2-14.el4_7.10:1.0.2-14.el4_7.1
Red Hat:enterprise_linux:4::asevolution-data-server-develbefore 0:1.0.2-14.el4_7.10:1.0.2-14.el4_7.1
Red Hat:enterprise_linux:4::asevolution-debuginfobefore 0:2.0.2-41.el4_7.20:2.0.2-41.el4_7.2
Red Hat:enterprise_linux:4::asevolution-develbefore 0:2.0.2-41.el4_7.20:2.0.2-41.el4_7.2
Red Hat:enterprise_linux:4::asevolution28-evolution-data-serverbefore 0:1.8.0-37.el4_7.20:1.8.0-37.el4_7.2
Red Hat:enterprise_linux:4::asevolution28-evolution-data-server-debuginfobefore 0:1.8.0-37.el4_7.20:1.8.0-37.el4_7.2
Red Hat:enterprise_linux:4::asevolution28-evolution-data-server-develbefore 0:1.8.0-37.el4_7.20:1.8.0-37.el4_7.2
Red Hat:enterprise_linux:5::clientevolution-data-server-docbefore 0:1.12.3-10.el5_3.30:1.12.3-10.el5_3.3
Red Hat:enterprise_linux:5::client_workstationevolution-data-serverbefore 0:1.12.3-10.el5_3.30:1.12.3-10.el5_3.3
Red Hat:enterprise_linux:5::client_workstationevolution-data-server-debuginfobefore 0:1.12.3-10.el5_3.30:1.12.3-10.el5_3.3
Red Hat:enterprise_linux:5::client_workstationevolution-data-server-develbefore 0:1.12.3-10.el5_3.30:1.12.3-10.el5_3.3

Other highest-scoring records for the same primary product.

  • CVE-2020-16117In GNOME evolution-data-server before 3.35.91, a malicious server can crash the mail client with a NULL pointer dereference by sending an in
    24Monitor
  • CVE-2020-14928evolution-data-server (eds) through 3.36.3 has a STARTTLS buffering issue that affects SMTP and POP3.
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:evolution-data-server2.26.1.1-1 · Debian:12Package registry (OSV)
red hat:evolution0:2.0.2-41.el4_7.2 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution-data-server0:1.12.3-10.el5_3.3 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:evolution-data-server-debuginfo0:1.12.3-10.el5_3.3 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:evolution-data-server-devel0:1.12.3-10.el5_3.3 · Red Hat:enterprise_linux:5::client_workstationPackage registry (OSV)
red hat:evolution-data-server-doc0:1.12.3-10.el5_3.3 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:evolution-debuginfo0:2.0.2-41.el4_7.2 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution-devel0:2.0.2-41.el4_7.2 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution28-evolution-data-server0:1.8.0-37.el4_7.2 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution28-evolution-data-server-debuginfo0:1.8.0-37.el4_7.2 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:evolution28-evolution-data-server-devel0:1.8.0-37.el4_7.2 · Red Hat:enterprise_linux:4::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records