How severe is CVE-2004-2650?

CVE-2004-2650 has a CVSS 2.0 base score of 4.9, rated medium severity.

Is CVE-2004-2650 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2004-2650?

CVE-2004-2650 affects Apache James. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2004-2650?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2004-2650 published?

CVE-2004-2650 was published on 2004-12-31 and last updated on 2026-06-16.

CVE-2004-2650

CVE-2004-2650 is a medium-severity vulnerability in Apache James with a CVSS 2.0 base score of 4.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.9)
EPSS exploit prediction: 1% (43rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Apache James
Published: 2004-12-31
Last modified: 2026-06-16

Description

Spooler in Apache Foundation James 2.2.0 allows local users to cause a denial of service (memory consumption) by triggering various error conditions in the retrieve function, which prevents a lock from being released and causes a memory leak.

Frequently asked questions

What is CVE-2004-2650?: Spooler in Apache Foundation James 2.2.0 allows local users to cause a denial of service (memory consumption) by triggering various error conditions in the retrieve function, which prevents a lock from being released and causes a memory leak.
How severe is CVE-2004-2650?: CVE-2004-2650 has a CVSS 2.0 base score of 4.9, rated medium severity.
Is CVE-2004-2650 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2004-2650?: CVE-2004-2650 affects Apache James. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2004-2650?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2004-2650 published?: CVE-2004-2650 was published on 2004-12-31 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:apache:james:2.2.0:*:*:*:*:*:*:*

More vulnerabilities in Apache James

CVE-2023-51518 — Critical (CVSS 9.8): Apache James prior to version 3.7.5 and 3.8.0 exposes a JMX endpoint on localhost subject to pre-authentication…
CVE-2019-0228 — Critical (CVSS 9.8): Apache PDFBox 2.0.14 does not properly initialize the XML parser, which allows context-dependent attackers to conduct…
CVE-2021-40525 — Critical (CVSS 9.1): Apache James ManagedSieve implementation alongside with the file storage for sieve scripts is vulnerable to path…
CVE-2023-26269 — High (CVSS 7.8): Apache James server version 3.7.3 and earlier provides a JMX management service without authentication by default. This…
CVE-2006-2806 — High (CVSS 7.8): The SMTP server in Apache Java Mail Enterprise Server (aka Apache James) 2.2.0 allows remote attackers to cause a…
CVE-2022-28220 — High (CVSS 7.5): Apache James prior to release 3.6.3 and 3.7.1 is vulnerable to a buffering attack relying on the use of the STARTTLS…

All CVEs affecting Apache James →