CVE-2007-1585
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Linksys WAG200G with firmware 1.01.01, WRT54GC 2 with firmware 1.00.7, and WRT54GC 1 with firmware 1.03.0 and earlier allow remote attackers to obtain sensitive information (passwords and configuration data) via a packet to UDP port 916. NOTE: some of these details are obtained from third party information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in legacy Linksys router firmware (WAG200G, WRT54GC 1/2) allows unauthenticated remote attackers to retrieve sensitive information including passwords and configuration data by sending a specific packet to UDP port 916. The exposed UDP service lacks proper access controls, enabling any attacker on the network or internet to query this port and receive plaintext credentials and device configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.01.01<= 1.03.0= 1.00.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLog into the router web interface or check the device label to confirm the exact model number is WAG200G or WRT54GCAffected if The model is WAG200G or WRT54GC
-
Check the firmware version on WAG200GAccess the router admin panel, navigate to the Status or Administration page, and record the firmware version displayedAffected if The firmware version is exactly 1.01.01
-
Check the firmware version on WRT54GCAccess the router admin panel, navigate to the Status or Administration page, and record the firmware version displayedAffected if The firmware version is 1.00.7 or any version up to and including 1.03.0
-
Verify UDP port 916 is openUse a network port scanner such as nmap (nmap -sU -p 916 <routerIP>) or netcat to test if UDP port 916 is listening on the deviceAffected if UDP port 916 returns as open or filtered on the router's IP address
-
Test for information disclosure (optional confirmation)Send a UDP packet to port 916 and observe if plaintext configuration data or credentials are returned; use a packet capture tool to analyze the responseAffected if The UDP service responds with sensitive configuration data or plaintext passwords
The device is affected if it is a WAG200G running firmware 1.01.01 or a WRT54GC running firmware 1.00.7 through 1.03.0, AND UDP port 916 is open and responding with sensitive information.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataPrimary mitigation is to apply any available firmware update from Cisco/Linksys; if no update exists, network segmentation or firewall rules should block UDP port 916 from untrusted networks, and affected devices should be replaced. Check vendor support pages for patch availability.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-1585 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data