Nuevo fallo de Seguridad 3Com 812 Router
La seguridad del Router 3Com 812 se compromete estos últimos días. Ahora usuarios remotos pueden llegar a tener acceso saltando la autenticación.
3Com OfficeConnect ADSL Router Authentication Can Be Bypassed By Remote Users
Para más detalles visitar la siguiente página:iDEFENSE Vulnerabilidad 3Com 812
3Com OfficeConnect Remote 812 ADSL Router Authentication Bypass Vulnerability
iDEFENSE Security Advisory 05.27.04:
I. BACKGROUND
The 3Com OfficeConnect Remote 812 ADSL Router is a standalone
bridge/router, with interfaces to a Local Area Network and an ADSL
interface to a Wide Area Network.
II. DESCRIPTION
Remote exploitation of an authentication bypass vulnerability in 3Com’s
OfficeConnect Remote 812 ADSL Router could allow remote users to
arbitrarily manipulate network traffic.
By making multiple successive authorization attempts to connect to the
router, it is eventually possible to authenticate with any
username/password combination. While the root cause of the vulnerability
is not known, exploitation is trivial and does not require either a
known username or password.
III. ANALYSIS
Successful exploitation allows an attacker to perform any administrative
function that a legitimate administrator could perform.
More information about the 3Com OfficeConnect Remote 812 ADSL Router is
available at
http://www.3com.com/products/en_US/detail.jsp?tab=support&pathtype=support&sku=3CP4144.
IV. DETECTION
iDEFENSE has confirmed that the 3Com OfficeConnect Remote 812 ADSL
Router with the last firmware patch is vulnerable
V. WORKAROUNDS
A previously given workaround for other issues with the HTTP interface
is available at the link shown. This shows how to configure the router
to prevent external access to the HTTP port.
http://support.3com.com/infodeli/tools/remote/ocradsl/http_filtering.pdf
VI. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CAN-2004-0477 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org), which standardizes names for
security problems.
VII. DISCLOSURE TIMELINE
02/18/04 Exploit acquired by iDEFENSE
03/08/04 iDEFENSE Clients notified
03/11/04 Initial vendor notification - no response
03/30/04 Secondary vendor notification - no response
05/27/04 Public Disclosure
VIII. CREDIT
Rafel Ivgi is credited with this discovery.












