CVE-2017-18344
What it is
The timer_create syscall implementation in kernel/time/posix-timers.c in the Linux kernel before 4.14.8 doesn't properly validate the sigevent->sigev_notify field, which leads to out-of-bounds access in the show_timer function (called when /proc/$PID/timers is read). This allows userspace applications to read arbitrary kernel memory (on a kernel built with CONFIG_POSIX_TIMERS and CONFIG_CHECKPOINT_RESTORE).
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure.
- Exploit odds
- 3.4% chance of exploitation in the next 30 days (EPSS).
- 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: 3.4% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.4% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Linux Kernel < 4.14.8
- Canonical Ubuntu Linux 12.04
- Canonical Ubuntu Linux 14.04
- Redhat Mrg Realtime 2.0
- Redhat Enterprise Linux Desktop 7.0
- Redhat Enterprise Linux Server 7.0
- Redhat Enterprise Linux Server Aus 7.2
- Redhat Enterprise Linux Server Aus 7.3
Attack profile CVSS 3.0 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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-18344.md and follow it. Check whether this project is affected by CVE-2017-18344. 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
- https://github.com/torvalds/linux/commit/cef31d9af908243421258f1df35a4a644604efbe
- https://github.com/torvalds/linux/commit/cef31d9af908243421258f1df35a4a644604efbe
References
- http://www.securityfocus.com/bid/104909
- http://www.securitytracker.com/id/1041414
- https://access.redhat.com/errata/RHSA-2018:2948
- https://access.redhat.com/errata/RHSA-2018:3083
- https://access.redhat.com/errata/RHSA-2018:3096
- https://access.redhat.com/errata/RHSA-2018:3459
- https://access.redhat.com/errata/RHSA-2018:3540
- https://access.redhat.com/errata/RHSA-2018:3586
- https://access.redhat.com/errata/RHSA-2018:3590
- https://access.redhat.com/errata/RHSA-2018:3591
- https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.8
- https://github.com/torvalds/linux/commit/cef31d9af908243421258f1df35a4a644604efbe
- https://usn.ubuntu.com/3742-1/
- https://usn.ubuntu.com/3742-2/
- https://www.exploit-db.com/exploits/45175/
- http://www.securityfocus.com/bid/104909
- http://www.securitytracker.com/id/1041414
- https://access.redhat.com/errata/RHSA-2018:2948
- https://access.redhat.com/errata/RHSA-2018:3083
- https://access.redhat.com/errata/RHSA-2018:3096
- https://access.redhat.com/errata/RHSA-2018:3459
- https://access.redhat.com/errata/RHSA-2018:3540
- https://access.redhat.com/errata/RHSA-2018:3586
- https://access.redhat.com/errata/RHSA-2018:3590
- https://access.redhat.com/errata/RHSA-2018:3591