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: Jordan Windows Telnet Server Username Stack Based Buffer Overrun Vulnerability

Severity: CRITICAL

Description:

Jordan Windows Telnet Server is a Telnet server for Microsoft Windows platforms.

Jordan Windows Telnet Server has been reported prone to a remote buffer overrun vulnerability. The issue has been reported to present itself when a username is supplied to the Telnet server that is 518 bytes in length. Due to a lack of bounds checking, when this username is copied into an insufficient reserved buffer in stack-based memory, data that exceeds the size of the buffer will overrun its bounds and corrupt adjacent memory.

An attacker may exploit this condition to corrupt a saved instruction pointer for the vulnerable function, and thereby influence execution flow into attacker supplied instructions. These instructions will subsequently be executed in the context of the affected service.

The severity of this vulnerability may be exaggerated due to the fact that the overflow occurs pre-authentication.

It should be noted that although this issue has been reported to affect Jordan Windows Telnet Server version 1.0, other versions might also be affected.

Affected Products:

  • Jordan Windows Telnet Server 1.0.0
  • Jordan Windows Telnet Server 1.2.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.