What is CVE-2014-8160?A medium-severity flaw in Linux kernel, explained.
CVE-2014-8160 is a medium-severity flaw (CVSS 5.0) in Linux kernel, published on 2 March 2015. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 5.5%. If you run an affected version, plan in the vendor’s fix.
Published 2 March 2015. Record last updated 12 April 2025. We keep this page's data up to date.
What is CVE-2014-8160? In plain terms.
It can be attacked from anywhere on the internet without logging in. If it works, the attacker can change some data.
net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before 3.18 generates incorrect conntrack entries during handling of certain iptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols, which allows remote attackers to bypass intended access restrictions via packets with disallowed port numbers.
What kind of flaw is it?
- CWE-20Improper Input Validation
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- What an attacker getsCan change some data
Severity vector: AV:N/AC:L/Au:N/C:N/I:P/A:N
Is CVE-2014-8160 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 5.5%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2014-8160 scores 24. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2014-8160 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2014-8160? 15 products.
The published record lists 15 products from 6 vendors. Versions are shown as published: "before 3.18" means every version up to, but not including, 3.18. If you run one of these, check your version, then go to the fix below.
- Operating system
Linux kernel
by Linux
Affected versionsbefore 3.18 - Operating system
Enterprise Linux Server Eus
by Red Hat
Affected versions6.56.67.37.47.57.6 - Operating system
Enterprise Linux Server Aus
by Red Hat
Affected versions6.56.67.37.6 - Operating system
Enterprise Linux Server Tus
by Red Hat
Affected versions6.56.67.67.7 - Operating system
Ubuntu Linux
by Canonical
Affected versions12.0414.0414.10 - Operating system
Debian Linux
by Debian
Affected versions7.08.0 - Operating system
Enterprise Linux Desktop
by Red Hat
Affected versions6.07.0 - Operating system
Enterprise Linux Server
by Red Hat
Affected versions6.07.0 - Operating system
Enterprise Linux Workstation
by Red Hat
Affected versions6.07.0
How do I fix CVE-2014-8160? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
22 links- oss-security mailing list post, 14 Jan 2015 (opens in a new tab)openwall.com · 2015
- Msg33430 (opens in a new tab)spinics.net
- torvalds/linux commit (opens in a new tab)github.com
- Web page (opens in a new tab)kernel.org
- Msg00020 (opens in a new tab)opensuse.org · 2015
- Msg00000 (opens in a new tab)opensuse.org · 2015
Does CVE-2014-8160 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before 3.18 generates incorrect conntrack entries during handling of certain iptables rule set...
- Matched to
- Linux kernel on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2014-8160 is a medium-severity flaw in Linux kernel, published on 2 March 2015. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can change some data.
It scores 5.0 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2014-8160 is 24 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 5.5%. That can change at any time, which is why we keep watching.
For Linux kernel: before 3.18. The record lists 15 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.