CVE-2004-1596
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 3COM Wireless router 3CRADSL72 running Boot Code 1.3d allows remote attackers to gain sensitive information such as passwords and router settings via a direct HTTP request to app_sta.stm.
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 3CRADSL72 router's web interface contains a page (app_sta.stm) that returns sensitive configuration data including plaintext passwords and router settings without requiring proper authentication. This information disclosure vulnerability allows unauthenticated remote attackers to obtain administrative credentials via a direct HTTP request.
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 dataall versionsCVSS 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.
-
Confirm router model is 3Com 3CRADSL72Access the router's web interface or check the device label/management console to verify the exact model number matches 3CRADSL72Affected if The device is a 3Com 3CRADSL72 router (all versions are affected)
-
Verify web management interface is exposedAttempt to access the router's HTTP interface via its LAN or WAN IP address on common ports (80 or 443)Affected if The web interface is reachable and responds to HTTP requests
-
Test unauthenticated access to app_sta.stmSend a direct HTTP GET request to http://[router-ip]/app_sta.stm without providing any login credentialsAffected if The page loads and returns configuration data without requiring authentication
-
Check for plaintext passwords in responseInspect the HTTP response body from the app_sta.stm page for strings like 'password', 'pwd', or actual credentials in plaintextAffected if The response contains plaintext passwords or other sensitive configuration data such as router settings
If the 3CRADSL72 router has its web interface accessible and the app_sta.stm page returns sensitive configuration data including plaintext passwords without authentication, the environment is affected by CVE-2004-1596.
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 dataRestrict external access to the router's web management interface via firewall rules or disable remote management. Given the device's age (2004) and likely lack of vendor support, strongly consider replacing the affected router with a currently-supported model.
- 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-2004-1596 — 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-2004-1596 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