CVE-2005-0833
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 · uneditedBelkin 54G (F5D7130) wireless router allows remote attackers to access restricted resources by sniffing URIs from UPNP datagrams, then accessing those URIs, which do not require authentication.
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 · high confidenceThe Belkin 54G (F5D7130) wireless router's UPnP implementation exposes administrative URIs in broadcasted datagrams without requiring authentication. An attacker on the local network can sniff these URIs and directly access restricted router resources, bypassing authentication entirely.
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= f5d7130CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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's web administration interface (typically at 192.168.2.1) and check the device status or system info page to confirm the model number is F5D7130 (Belkin 54G)Affected if The router model is Belkin 54G (F5d7130)
-
Verify UPnP is enabledIn the router's web admin interface, navigate to the UPnP settings page (usually under Advanced or LAN settings) and check whether the UPnP checkbox is enabled or the feature is turned onAffected if UPnP is enabled on the router - this is the vulnerable feature that broadcasts administrative URIs
-
Confirm network accessibilityDetermine if untrusted devices can connect to the local network (wired or wireless) - an attacker would need to be on the same network segment to sniff the UPnP broadcast packetsAffected if Untrusted or unknown devices can access the local network where the router is deployed
-
Inspect UPnP broadcast trafficUse a network packet capture tool (such as Wireshark) on a computer connected to the router's network and filter for UPnP multicast traffic (typically to 239.255.255.250 on port 1900) to observe if administrative URIs are being broadcast without authenticationAffected if UPnP datagrams contain administrative URIs (such as /router.config, /WLAN.config, or similar) that do not require credentials to access
You are affected if you are using a Belkin 54G (F5D7130) router with UPnP enabled, as administrative URIs are broadcast without authentication and can be accessed by anyone on the local network.
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 dataReplace the deprecated Belkin 54G router with a current model that receives security updates, as this legacy device cannot be patched for this vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-0833 — 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-2005-0833 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