[NEWS] D-Link DWL-1000AP can be Compromised Due to Insecure SNMP ConfigurationFrom: email@example.com
- Previous message: firstname.lastname@example.org: "[UNIX] Webmin view_man.cgi Security Vulnerability"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: email@example.com To: firstname.lastname@example.org Date: Tue, 25 Dec 2001 08:08:56 +0100 (CET)
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
When was the last time you checked your server's security?
How about a monthly report?
http://www.AutomatedScanning.com - Know that you're safe.
- - - - - - - - -
D-Link DWL-1000AP can be Compromised Due to Insecure SNMP Configuration
A security vulnerability in
<http://www.dlink.com/products/wireless/dwl1000ap/> D-Link DWL-1000AP
allows an attacker to gain the administrative password using a simple SNMP
DWL-1000AP Wireless Access (3.2.28 #483)
Due to the fact the DWL-1000AP uses SNMP by default; a weakness in the
product allows attackers to hijack the access point. This happens even if
the DWL has been enabled to use a 128-bit WEP, a non-default admin
password has been set, a non-default SSID name is used, and the
configuration is to disallow all MACs except for those explicitly allowed.
A MIB walk using the read-only SNMP community of 'public' (default
read-only community for most devices) can allow an attacker access to the
"admin password" to the access point listed in clear text in OID
188.8.131.52.4.1.9184.108.40.206.2.0 as a string value.
By telling the SNMP utility to use "snowball" as the write community, it
is possible to reset the value stored in that OID to any arbitrary value.
This means that anyone armed with a simple SNMP utility that can perform
read and write operations, can read the private community name (which
defaults to "public" with no way to change it using D-Link's configuration
software), and access to the network connected to the Ethernet port of the
access point. Further, an attacker could hijack the access point and
either simply configure the product to allow him access to the wireless
network or completely change the configuration and cause a denial of
The only protection currently offered by the access point against this
attack is the lock-access point procedure. This is not an option in most
cases since the access point may be mounted in a hard to access area, for
example, in which case a simple configuration change would require
physical access to the device, which may be impractical in all situations.
A more practical solution would be to give the user the ability to set
both the read-only (found in OID 220.127.116.11.4.1.918.104.22.168.1.0) and write
community names. This can currently be done, by using an SNMP utility to
write to the read-only community OID. By changing that community, an
attacker would have to sniff SNMP packets across the network or otherwise
figure out the read-only community, a more difficult task than simply
using the default read-only community for most SNMP devices. By giving the
user the ability to control the read-only community value through the HTTP
configuration, it would be a very simple task for that user to change the
value during the initial setup and thus increase the security of the
D-Link responded with this message:
Dear Valued Customer,
In regards to your e-mail, I agree however, the dwl-1000 is intended for
residential use. It does not put of enough wireless signal to cause much
concern of hackers. The hacker would have to be sitting outside you house
by the window.
Thank you for your technical question and feedback. If you are continuing
to have problems, please contact our live support at 800-758-5489 or
resubmit the problem at http://www.dlink.com/tech/contact/.
D-Link US Technical Support
This response seems to be unsatisfactory, considering how easy it would be
to allow a user to change the read community name.
Anyone who has a DWL-1000AP is encouraged to use an SNMP utility to change
the read community stored in OID (22.214.171.124.4.1.9126.96.36.199.1.0).
The information has been provided by <mailto:email@example.com>
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: firstname.lastname@example.org
In order to subscribe to the mailing list, simply forward this email to: email@example.com
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.