CVE-2017-1000112
What it is
Linux kernel: Exploitable memory corruption due to UFO to non-UFO path switch. When building a UFO packet with MSG_MORE __ip_append_data() calls ip_ufo_append_data() to append. However in between two send() calls, the append path can be switched from UFO to non-UFO one, which leads to a memory corruption. In case UFO packet lengths exceeds MTU, copy = maxfraglen - skb->len becomes negative on the non-UFO path and the branch to allocate new skb is taken. This triggers fragmentation and computation of fraggap = skb_prev->len - maxfraglen. Fraggap can exceed MTU, causing copy = datalen - transhdrlen - fraggap to become negative. Subsequently skb_copy_and_csum_bits() writes out-of-bounds. A similar issue is present in IPv6 code. The bug was introduced in e89e9cf539a2 ("[IPv4/IPv6]: UFO Scatter-gather approach") on Oct 18 2005.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 20.8% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 20.8% in the next 30 days (EPSS).
- Severity: 7.0 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 20.8% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Modified
Affected
- Linux Kernel < 3.10.108
- Linux Kernel < 3.16.47
- Linux Kernel < 3.18.65
- Linux Kernel < 4.4.82
- Linux Kernel < 4.9.43
- Linux Kernel < 4.12.7
Attack profile CVSS 3.1 · 7.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-1000112.md and follow it. Check whether this project is affected by CVE-2017-1000112. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
References
- http://seclists.org/oss-sec/2017/q3/277
- http://www.debian.org/security/2017/dsa-3981
- http://www.securityfocus.com/bid/100262
- http://www.securitytracker.com/id/1039162
- https://access.redhat.com/errata/RHSA-2017:2918
- https://access.redhat.com/errata/RHSA-2017:2930
- https://access.redhat.com/errata/RHSA-2017:2931
- https://access.redhat.com/errata/RHSA-2017:3200
- https://access.redhat.com/errata/RHSA-2019:1931
- https://access.redhat.com/errata/RHSA-2019:1932
- https://access.redhat.com/errata/RHSA-2019:4159
- https://github.com/xairy/kernel-exploits/tree/master/CVE-2017-1000112
- https://www.exploit-db.com/exploits/45147/
- http://seclists.org/oss-sec/2017/q3/277
- http://www.debian.org/security/2017/dsa-3981
- http://www.securityfocus.com/bid/100262
- http://www.securitytracker.com/id/1039162
- https://access.redhat.com/errata/RHSA-2017:2918
- https://access.redhat.com/errata/RHSA-2017:2930
- https://access.redhat.com/errata/RHSA-2017:2931
- https://access.redhat.com/errata/RHSA-2017:3200
- https://access.redhat.com/errata/RHSA-2019:1931
- https://access.redhat.com/errata/RHSA-2019:1932
- https://access.redhat.com/errata/RHSA-2019:4159
- https://github.com/xairy/kernel-exploits/tree/master/CVE-2017-1000112