dbcve.org
Hp UxOperating system · Hp

CVE-1999-0015

MEDIUM · 5.0 CVSS v2.0 Published 1997-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Teardrop IP denial of 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 confidence

The Teardrop attack exploits a buffer overflow vulnerability in the IP fragment reassembly code of older operating systems (primarily Windows 95/NT and early Linux). It sends specially crafted overlapping IP fragments that cause the victim to crash or freeze during reassembly of the malformed packets.

MitigationApply vendor patches for affected legacy operating systems, or implement network-level filtering (e.g., firewall rules) to drop malformed fragmented IP packets with overlapping offsets.

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
Hp UxOperating system
Affected:= 9.00= 9.01= 9.03= 9.04= 9.05= 9.07= 10= 10.01= 10.16= 10.20= 10.24= 10.30
Windows 95Operating system
Affected:= 0.0a
Windows NtOperating system
Affected:= 3.5.1= 4.0
NetbsdOperating system
Affected:= 1.0= 1.1= 1.2= 1.2.1
SunosOperating system
Affected:= 4.1.3u1= 4.1.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the operating system and version
    Run 'uname -a' on Unix systems or check System Properties on Windows to determine the exact OS version
    Affected if The OS is HP-UX 9.00-10.30, Windows 95, Windows NT 3.5.1/4.0, NetBSD 1.0-1.2.1, or SunOS 4.1.3u1/4.1.4
  2. Verify IP fragmentation handling is enabled
    Check if the system accepts and reassembles IP fragments - on Unix check /proc/sys/net/ipv4/ipfrag* or use 'netstat -s' to see fragment statistics
    Affected if The system processes IP fragments (this is typically enabled by default on vulnerable systems)
  3. Confirm network exposure to external traffic
    Review firewall rules and network configuration to determine if the system accepts incoming IP traffic
    Affected if The system can receive unsolicited IP packets from the network (direct internet connection or unfiltered LAN)

A system is affected only if it runs one of the exact vulnerable OS versions listed AND has IP fragmentation processing enabled AND can receive external network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for affected legacy operating systems, or implement network-level filtering (e.g., firewall rules) to drop malformed fragmented IP packets with overlapping offsets.

Fix this in Hp Ux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-1999-0015 — 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-1999-0015 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