CVE-1999-1342
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 · uneditedICQ ActiveList Server allows remote attackers to cause a denial of service (crash) via malformed packets to the server's UDP port.
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 · moderate confidenceThe ICQ ActiveList Server suffers from a denial of service vulnerability where specially crafted malformed UDP packets sent to the server's listening port can cause the service to crash. The vulnerability requires no authentication and can be exploited remotely via network access to the UDP port.
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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check for ICQ ActiveList Server installationSearch system processes, services, and installed programs for 'ActiveList' or 'ICQ' related components. On Windows, check Services control panel and installed programs list. On Unix-like systems, check running processes with commands like 'ps aux' or 'netstat -an'.Affected if ICQ ActiveList Server or related ICQ server components are found running or installed on the system
-
Identify UDP port listenersUse network diagnostic tools to list all UDP ports in listening state. On Windows: 'netstat -anp UDP' or 'netstat -ano | findstr LISTENING'. On Unix: 'netstat -ulpn' or 'ss -ulpn'.Affected if Any unknown or unexpected UDP listening ports are found that may correspond to the ActiveList Server
-
Verify network exposure of UDP servicesReview firewall rules and network perimeter configurations to determine if UDP ports used by the ICQ ActiveList Server are accessible from external networks. Check both host-based firewalls (Windows Firewall, iptables) and network-level firewalls.Affected if UDP ports associated with the ICQ ActiveList Server are permitted through firewalls and accessible from untrusted networks
-
Check for legacy ICQ server configurationsExamine system startup items, scheduled tasks, and service configurations for ICQ-related server software. Review any configuration files in directories associated with ICQ or messaging server deployments.Affected if ICQ server software or services are configured to start automatically and remain running
The environment is affected if ICQ ActiveList Server is installed and its UDP listening port is accessible from the network, since the vulnerability can be exploited remotely without authentication via malformed UDP packets.
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 legacy ICQ infrastructure software from 1999, the primary mitigation is to identify and remove the obsolete service if no longer needed, or implement network-level UDP port filtering to restrict unauthorized sources.
- 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-1999-1342 — 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-1342 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