CVE-2019-11479
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 · uneditedJonathan Looney discovered that the Linux kernel default MSS is hard-coded to 48 bytes. This allows a remote peer to fragment TCP resend queues significantly more than if a larger MSS were enforced. A remote attacker could use this to cause a denial of service. This has been fixed in stable kernel releases 4.4.182, 4.9.182, 4.14.127, 4.19.52, 5.1.11, and is fixed in commits 967c05aee439e6e5d7d805e195b3a20ef5c433d6 and 5f3e2bf008c2221478101ee72f5cb4654b9fc363.
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 analysisA 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>= 4.4, < 4.4.182>= 4.9, < 4.9.182>= 4.14, < 4.14.127>= 4.19, < 4.19.52>= 5.1, < 5.1.11>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1>= 11.5.2, < 11.6.5.1>= 12.1.0, < 12.1.5.1>= 13.1.0, < 13.1.3.2>= 14.0.0, < 14.0.1.1>= 14.1.2, < 14.1.2.1>= 15.0.0, < 15.0.1.1CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 data4.4.1824.9.1824.14.127
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11479 — 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 sources- git.kernel.org
- git.kernel.org
- git.kernel.org
- github.com
- wiki.ubuntu.com
- www.arubanetworks.com
- www.openwall.com
- www.openwall.com
- www.openwall.com
- www.securityfocus.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- access.redhat.com
- cert-portal.siemens.com
- kb.pulsesecure.net
- kc.mcafee.com
- psirt.global.sonicwall.com
- security.netapp.com
- support.f5.com
- usn.ubuntu.com
- usn.ubuntu.com
- www.kb.cert.org
- www.oracle.com
- www.synology.com
- www.us-cert.gov
- www.us-cert.gov
- support.f5.com
- www.oracle.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-11479 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