CVE-1999-1533
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 · uneditedEicon Technology Diva LAN ISDN modem allows a remote attacker to cause a denial of service (hang) via a long password argument to the login.htm file in its HTTP service.
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 confidenceEicon Technology Diva LAN ISDN modem contains a buffer overflow vulnerability in its embedded HTTP server. The login.htm page fails to properly validate the length of the password parameter, allowing a remote attacker to send an overly long string that causes the device to hang, resulting in denial of service.
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= 3.2.3= 3.3CVSS 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 Eicon Diva LAN ISDN modem on the networkScan the network for devices with HTTP services on port 80/tcp or 443/tcp. Use nmap or similar tool: nmap -p 80,443 -sV <target> and examine the HTTP server banner for 'Eicon' or 'Diva' strings in the response headers or default login page.Affected if The device responds with Eicon Diva HTTP server headers or a login page branded as Eicon Diva LAN ISDN modem.
-
Confirm embedded HTTP server is enabledAccess the device via HTTP or HTTPS. Attempt to reach the /login.htm or / directory. A successful HTTP response indicates the server is running.Affected if The HTTP server responds with a login page at /login.htm or similar, meaning the vulnerable interface is active.
-
Check if the device is still operationalPing the device IP address or send HTTP requests to verify it is still powered on and responding. A response indicates the device is online.Affected if The device responds to network requests, meaning it is still in production use and could be affected by the denial of service condition.
-
Verify device is not isolated on restricted network segmentsReview network segmentation configs, VLAN assignments, or firewall rules to determine if the device is directly accessible from untrusted networks.Affected if The device is reachable from general network segments without firewall or VLAN isolation, increasing exposure risk.
A user is affected if an Eicon Diva LAN ISDN modem with its embedded HTTP server enabled is still operational and directly accessible on the network, as the buffer overflow in the login.htm password parameter can cause the device to hang.
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 dataSince this is a 1999 vulnerability affecting likely obsolete ISDN hardware, verify if the device is still in production use. If active, check Eicon/Apple (who acquired Eicon's network business) for legacy firmware updates. Otherwise, isolate the device on a restricted VLAN or replace with modern hardware.
- 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-1999-1533 — 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-1999-1533 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