Home    |    View Topics    |    Search    |    Contact Us    |   



Category:   Device (Router/Bridge/Hub)  >   NETGEAR Router Vendors:   NETGEAR
NETGEAR DG632 Router Discloses File Source Contents to Remote Users
SecurityTracker Alert ID:  1022404
SecurityTracker URL:
CVE Reference:   CVE-2009-2257, CVE-2009-2258   (Links to External Site)
Updated:  Jul 1 2009
Original Entry Date:  Jun 16 2009
Impact:   Disclosure of system information
Exploit Included:  Yes  
Version(s): DG632; firmware version 3.4.0_ap
Description:   A vulnerability was reported in the NETGEAR DG632 Router. A remote user can obtain the source code of some files on the target system.

A remote user can supply a specially crafted request to bypass authentication and view the source code of certain files on the target device. A remote user can also determine valid directories and file names on the target system.

The vendor was notified on June 12, 2009.

Tom Neaves reported this vulnerability.

Impact:   A remote user can obtain the source code of some files on the target system.
Solution:   No solution was available at the time of this entry.

[Editor's note: The vendor has noted that the vulnerable product has reached end of life.]

Vendor URL: (Links to External Site)
Cause:   Access control error

Message History:   None.

 Source Message Contents

Subject:  Netgear DG632 Router Authentication Bypass Vulnerability

Product Name: Netgear DG632 Router
Date: 15 June, 2009
Author: <>
Original URL:
Discovered: 18 November, 2006
Disclosed: 15 June, 2009


The Netgear DG632 router has a web interface which runs on port 80.  This
allows an admin to login and administer the device's settings. 
Authentication of
this web interface is handled by a script called "webcm" residing in 
which redirects to the relevant pages depending on successful user 
Vulnerabilities in this interface enable an attacker to access files and 
without authentication.


The "webcm" script handles user authentication and attempts to load 
(via javascript below).  The "indextop.htm" page requires authentication 
(HTTP Basic Authorization).


<script language="javascript" type="text/javascript">
function loadnext() {
<body bgcolor="#ffffff" onload="loadnext()" >

Loading file ...
<form method="POST" action="../cgi-bin/webcm" id="uiPostForm">
<input type="hidden" name="nextpage" value="../html/indextop.htm" 


If a valid password to the default "admin" user is supplied, the script then 
continues to load
the "indextop.htm" page and continues to load the other frames based on a 
hidden field.  If user
authentication is unsuccessful, the user is returned back to 
"../cgi-bin/webcm".  It is possible
to bypass the "webcm" script and access specific files directly without the 
need for authentication.

Normal use:

This would ask for the user to authenticate and would refuse access to this 
file if authentication
details were not known.  All the script is doing is making sure 
authentication is forced upon the user.
The same "stattbl.htm" file can be accessed without having to provide any 
authentication using the
following URL:


Another example:
(returns 401 - Forbidden)

Bypassing the "webcm" script:
(returns 200 - OK)

In the example above (modemmenu.htm), the full source can be viewed which 
discloses further directories
and files within the javascript of the page. A sample of files disclosed 
within modemmenu.htm and available
to download are:

/html/utility.js (full source)

There are many other files that are accessible by calling them directly 
instead of going via the "webcm" script,
the above are just a sample. In addition, it is possible to specify paths to 
the "webcm" script as shown below:


This allows an attacker to enumerate what files and directories exist within 
the www root directory and beyond
by using 200, 403 and 404 errors as a guide.

Affected Versions: Firmware V3.4.0_ap (others unknown)


12 June, 2009 - Contacted vendor.
15 June, 2009 - Vendor responded.  Stated the DG632 is an end of life 
product and is no
longer supported in a production and development sense, as such, there will 
be no further
firmware releases to resolve this issue.


Discovered by Tom Neaves 


Go to the Top of This SecurityTracker Archive Page

Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2021, LLC