ID CVE-2008-1611
Summary Stack-based buffer overflow in TFTP Server SP 1.4 for Windows allows remote attackers to cause a denial of service or execute arbitrary code via a long filename in a read or write request.
Vulnerable Configurations
  • cpe:2.3:a:tftp-server:winagents_tftp_server:sp_1.4:-:windows
Base: 10.0 (as of 01-04-2008 - 14:13)
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
exploit-db via4
  • description TFTP Server for Windows 1.4 ST Buffer Overflow Exploit (0day). CVE-2008-1611. Remote exploit for windows platform
    file exploits/windows/remote/
    id EDB-ID:5314
    last seen 2016-01-31
    modified 2008-03-26
    platform windows
    port 69
    published 2008-03-26
    reporter muts
    title TFTP Server for Windows 1.4 - ST Buffer Overflow Exploit 0day
    type remote
  • description TFTP Server 1.4 - ST (RRQ) Buffer Overflow Exploit. CVE-2008-1611. Remote exploit for windows platform
    id EDB-ID:18345
    last seen 2016-02-02
    modified 2012-01-10
    published 2012-01-10
    reporter b33f
    title TFTP Server 1.4 - ST RRQ Buffer Overflow Exploit
  • description TFTP Server for Windows 1.4 ST WRQ Buffer Overflow. CVE-2008-1611. Remote exploit for windows platform
    id EDB-ID:18759
    last seen 2016-02-02
    modified 2012-04-20
    published 2012-04-20
    reporter metasploit
    title TFTP Server for Windows 1.4 - ST WRQ Buffer Overflow
metasploit via4
description This module exploits a vulnerability found in TFTP Server 1.4 ST. The flaw is due to the way TFTP handles the filename parameter extracted from a WRQ request. The server will append the user-supplied filename to TFTP server binary's path without any bounds checking, and then attempt to check this path with a fopen(). Since this isn't a valid file path, fopen() returns null, which allows the corrupted data to be used in a strcmp() function, causing an access violation. Since the offset is sensitive to how the TFTP server is launched, you must know in advance if your victim machine launched the TFTP as a 'Service' or 'Standalone' , and then manually select your target accordingly. A successful attempt will lead to remote code execution under the context of SYSTEM if run as a service, or the user if run as a standalone. A failed attempt will result a denial-of-service.
last seen 2019-03-25
modified 2017-07-24
published 2012-04-20
reliability Normal
reporter Rapid7
title TFTP Server for Windows 1.4 ST WRQ Buffer Overflow
packetstorm via4
data source
last seen 2016-12-05
published 2012-04-20
reporter Mati Aharoni
title TFTP Server for Windows 1.4 ST WRQ Buffer Overflow
refmap via4
bid 28462
exploit-db 5314
secunia 29508
xf tftpserver-filename-bo(41496)
Last major update 18-03-2009 - 01:35
Published 01-04-2008 - 12:44
Last modified 28-09-2017 - 21:30
Back to Top