Security readout for executives and security teams
Apache James 2.2.0 has a spooler flaw that can let a local user exhaust memory and disrupt mail handling. The business risk is service interruption, not disclosed data theft or remote takeover, based on the supplied sources. Exposure is likely limited to organizations still running Apache James 2.2.0, especially where untrusted or numerous local users can interact with the mail server environment. Treat as a targeted legacy-service availability risk. Prioritize remediation if Apache James 2.2.0 supports business mail flow or runs on shared systems with local users. Mitigation focus: Inventory mail servers for Apache James 2.2.0.; Review Apache JAMES-268 and the Apache James changelog for vendor guidance.; Upgrade or retire Apache James 2.2.0 if still present..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2004-2650 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
