Menu

Star on GitHub · 3.2k

CVE-2004-1706

7.5 · HIGH

The U.S.

Published Aug 2, 2004u.s.roboticsEPSS 3.42%

Overview

CVE-2004-1706 is a high-severity vulnerability affecting u.s.robotics usr808054. It was published on August 2, 2004 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The U.S. Robotics USR808054 wireless access point allows remote attackers to cause a denial of service (device crash) and possibly execute arbitrary code via an HTTP GET request with a long version string.

Remediation

Check the references section for vendor advisories and patches from u.s.robotics. Update usr808054 to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2004-1706?

CVE-2004-1706 is a high-severity vulnerability affecting u.s.robotics usr808054. It was published on August 2, 2004 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2004-1706?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2004-1706?

Check the references section for vendor advisories and patches from u.s.robotics. Update usr808054 to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2004-1706?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2004-1706 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2004

View all