dbcve.org
Wireless Lan Solution EngineApplication · Cisco

CVE-2004-0391

HIGH · 10.0 CVSS v2.0 Published 2004-06-01
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Cisco Wireless LAN Solution Engine (WLSE) 2.0 through 2.5 and Hosting Solution Engine (HSE) 1.7 through 1.7.3 have a hardcoded username and password, which allows remote attackers to add new users, modify existing users, and change configuration.

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

A detailed technical summary for this CVE is being prepared.

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
Wireless Lan Solution EngineApplication
Affected:= 2.0= 2.1= 2.2= 2.3= 2.4= 2.5
Hosting Solution EngineHardware / appliance
Affected:= 1.7= 1.7.0= 1.7.1= 1.7.2= 1.7.3

CVSS 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

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.ciac.org →
Recommended fix Moderate confidence

Migrate from Cisco WLSE 2.x / HSE 1.7.x to Cisco Prime Infrastructure 3.x or Cisco DNA Center 2.x (modern supported replacements)

  1. 1. Identify the current deployed version of Cisco WLSE or HSE using the web interface or CLI: for WLSE use 'show version', for HSE check the admin console under 'System > Administration > Software Version'
  2. 2. Since this is a hardcoded credential vulnerability with no vendor patch available for the legacy 2.x/1.7.x product lines, plan migration to a supported Cisco wireless management solution such as Cisco Prime Infrastructure (CPI) or Cisco Wireless LAN Controller (WLC) with Cisco DNA Center
  3. 3. Before migration, if the device must remain in service, restrict network access to the WLSE/HSE management interfaces using ACLs on adjacent network devices to limit exposure to untrusted networks
  4. 4. If web management is enabled, ensure it is only accessible over HTTPS and consider additional IP-based access restrictions
  5. 5. Document the current configuration including WLAN settings, device templates, and user accounts for migration purposes
  6. 6. Deploy the replacement solution (Cisco Prime Infrastructure or equivalent) on new hardware
  7. 7. Migrate configurations and verify WLAN management functionality in the new platform
  8. 8. Decommission the vulnerable WLSE/HSE devices after successful migration
Caveat Legacy WLSE-specific templates and automation features may require reconfiguration in new platform; plan for downtime during migration; ensure new platform hardware meets current compatibility requirements

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-0391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-0391 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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