VYPR
Unrated severityNVD Advisory· Published Apr 20, 2004· Updated Apr 16, 2026

CVE-2004-1945

CVE-2004-1945

Description

Buffer overflow in Kinesphere eXchange POP3's SMTP handler allows remote code execution via oversized MAIL FROM field.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Buffer overflow in Kinesphere eXchange POP3's SMTP handler allows remote code execution via oversized MAIL FROM field.

Vulnerability

Kinesphere eXchange POP3 prior to build 5.0.1629 contains a buffer overflow vulnerability in its SMTP handler. The flaw occurs when processing a long MAIL FROM field, allowing an attacker to overwrite stack memory. No authentication is required to trigger the vulnerability.

Exploitation

An attacker can send a crafted SMTP MAIL FROM command with an oversized value (e.g., 1019 bytes) to the target server on TCP port 25. As demonstrated in [2], this overwrites the instruction pointer allowing control of program execution. The exploit may require adjusting buffer sizes and return addresses depending on the target environment.

Impact

Successful exploitation leads to arbitrary code execution under the privileges of the eXchange POP3 service. This could compromise the entire Exchange server, leading to complete disclosure, modification, or destruction of data.

Mitigation

The issue is fixed in build 5.0.1629 [1]. Users should upgrade to this version or later from the vendor's download page. No workarounds are documented.

AI Insight generated on May 24, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

3
  • cpe:2.3:a:kinesphere_corporation:exchange_pop3:4.0:*:*:*:*:*:*:*+ 2 more
    • cpe:2.3:a:kinesphere_corporation:exchange_pop3:4.0:*:*:*:*:*:*:*
    • cpe:2.3:a:kinesphere_corporation:exchange_pop3:5.0:*:*:*:*:*:*:*
    • (no CPE)

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

7

News mentions

0

No linked articles in our index yet.