J-Security Center

Latest Attack Object Updates
  • IDP Daily Update #1545
    posted: 11/19/09
  • NSM Daily Update #1545
    posted: 11/19/09
  • Deep Inspection 5.3r5 and above, 5.4, 6.0 #1545
    posted: 11/19/09
  • Deep Inspection 5.1 and 5.2 #1435
    posted: 11/19/09
  • Deep Inspection 5.0, 5.3r4 and below #1132
    posted: 03/28/08 (04/01/08 for 5.0)
  • Antivirus
    posted: 11/19/09

Title: 1st Class Internet Solutions 1st Class Mail Server Remote Buffer Overflow Vulnerability

Severity: HIGH

Description:

1st Class Mail Server is an email/web mail server solution developed and maintained by 1st Class Internet Solutions.

1st Class Mail Server has been reported prone to a remote buffer overflow vulnerability. The issue exists due to a lack of sufficient boundary checks performed on user-supplied data (It has been conjectured that the vulnerable code exists in network2.cpp, this however has not been confirmed).

A remote attacker may pass excessive data (>626 Bytes) as the second argument for an APOP command passed to the affected server. Data that exceeds the size of a reserved buffer in stack-based memory will overrun its bounds resulting in the corruption of adjacent memory. An attacker may exploit this issue to corrupt a saved instruction pointer and in doing so may potentially influence execution flow of the affected service into attacker-supplied instructions. Code execution will occur in the context of the affected server process.

This vulnerability has been reported to affect 1st Class Mail Server version 4, other version might also be affected.

Affected Products:

  • 1st Class Internet Solutions 1st Class Mail Server 4.0.0

References:

Juniper Networks provides this content via a wide variety of sources and production methods. If notified of errors or omissions in the content of this page, Juniper Networks, at its discretion, will modify or remove the page or leave the content as is, depending on various factors including but not limited to the reputation and authority of the party providing the notification. Please use the contact information displayed elsewhere on this page to report any errors or omissions regarding the content on this page.