FreeBSDOperating system
CVE-1999-1339
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 · uneditedVulnerability when Network Address Translation (NAT) is enabled in Linux 2.2.10 and earlier with ipchains, or FreeBSD 3.2 with ipfw, allows remote attackers to cause a denial of service (kernel panic) via a ping -R (record route) command.
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 confidenceIn Linux 2.2.10 and earlier with ipchains, and FreeBSD 3.2 with ipfw, enabling NAT (Network Address Translation) creates a vulnerability where the ICMP record route option (-R flag) in ping packets can trigger a kernel panic, causing a 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
FreeBSDOperating system
= 3.2
Linux KernelOperating system
<= 2.2.10CVSS 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 the Linux kernel versionRun 'uname -r' or check /proc/version to identify the installed kernel versionAffected if The kernel version is 2.2.10 or earlier (e.g., 2.2.10, 2.2.9, 2.2.8, etc.)
-
Check the FreeBSD versionRun 'uname -a' or check /etc/os-release to identify the FreeBSD versionAffected if The FreeBSD version is exactly 3.2
-
Verify if ipchains is loaded on LinuxRun 'lsmod | grep ipchains' or check if /proc/net/ip_fwchains existsAffected if ipchains kernel module is loaded and NAT rules using ipchains are configured
-
Verify if ipfw is configured on FreeBSDRun 'ipfw list' or check if ipfw is enabled in the system configurationAffected if ipfw is enabled and NAT rules are configured using ipfw
-
Confirm NAT functionality is activeCheck for active NAT or masquerading rules in the firewall configuration: on Linux look for '-j MASQUERADE' or '-j SNAT' in ipchains rules; on FreeBSD check for 'nat' configuration in ipfw rulesAffected if NAT (Network Address Translation) is actively configured and processing traffic
The system is affected only if it is running Linux kernel 2.2.10 or earlier OR FreeBSD 3.2, AND has NAT enabled with ipchains or ipfw respectively, allowing ICMP packets with the record route option to be processed.
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 dataUpgrade to newer versions of Linux and FreeBSD that are not affected by this issue, or disable NAT and filter ICMP packets with the record route option enabled at the firewall.
Fix this in FreeBSD
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1339 — 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-1339 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