CVE-2003-1346
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 · uneditedD-Link wireless access point DWL-900AP+ 2.2, 2.3 and possibly 2.5 allows remote attackers to set factory default settings by upgrading the firmware using AirPlus Access Point Manager.
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 D-Link DWL-900AP+ wireless access point (versions 2.2, 2.3, possibly 2.5) contains a vulnerability allowing remote attackers to reset the device to factory default settings via the firmware upgrade function using AirPlus Access Point Manager. This represents a critical authentication/authorization bypass enabling complete device compromise.
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= 2.2= 2.3= 2.5CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 device modelCheck the physical device label or access the device web interface to confirm the model is D-Link DWL-900AP+. Network discovery tools or inventory records can also identify the device by its MAC address prefix or hostname.Affected if The device is not a D-Link DWL-900AP+ (unaffected model).
-
Check the installed firmware versionAccess the device web interface (typically http://192.168.0.1) and navigate to the System or Firmware section to view the firmware version. Alternatively, use the AirPlus Access Point Manager software to query the device status.Affected if The firmware version is 2.2, 2.3, or 2.5 (exact match to affected versions).
-
Verify if the firmware upgrade function is enabledIn the device web interface, check the System or Administration settings for the firmware upgrade or reset to factory defaults feature. Confirm whether this function is accessible without authentication or with default credentials.Affected if The firmware upgrade function is present and accessible (the vulnerability exists in this feature).
-
Determine if remote management is exposedCheck network firewall rules, NAT configurations, or port forwards to see if TCP ports used by the web interface (80/443) or AirPlus management software are exposed to untrusted networks or the internet.Affected if The device management interface is reachable from untrusted networks (enables remote exploitation).
The device is affected if it is a D-Link DWL-900AP+ running firmware version 2.2, 2.3, or 2.5, with the firmware upgrade feature accessible and the management interface exposed to potentially malicious network actors.
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 dataIf firmware updates are available from D-Link, apply them immediately. Otherwise, isolate affected devices behind firewalls, restrict management access to trusted networks, or replace end-of-life devices with supported hardware.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-1346 — 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-2003-1346 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