diff options
author | Mark Felder <feld@FreeBSD.org> | 2017-12-06 18:29:50 +0000 |
---|---|---|
committer | Mark Felder <feld@FreeBSD.org> | 2017-12-06 18:29:50 +0000 |
commit | 542a92472e5ed985844b46317cb4fd6da170a647 (patch) | |
tree | 9de00c82a73aa49f291c858a2e11fab34806c1f9 /security | |
parent | 259f1d719381b89d9aa77663e10c86fb319057d7 (diff) |
Notes
Diffstat (limited to 'security')
-rw-r--r-- | security/vuxml/vuln.xml | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml index d579a1c16958..54f0aa0a9266 100644 --- a/security/vuxml/vuln.xml +++ b/security/vuxml/vuln.xml @@ -58,6 +58,42 @@ Notes: * Do not forget port variants (linux-f10-libxml2, libxml2, etc.) --> <vuxml xmlns="http://www.vuxml.org/apps/vuxml-1"> + <vuln vid="5b1463dd-dab3-11e7-b5af-a4badb2f4699"> + <topic>FreeBSD -- POSIX shm allows jails to access global namespace</topic> + <affects> + <package> + <name>FreeBSD-kernel</name> + <range><ge>10.4</ge><lt>10.4_3</lt></range> + <range><ge>10.3</ge><lt>10.3_24</lt></range> + </package> + </affects> + <description> + <body xmlns="http://www.w3.org/1999/xhtml"> + <h1>Problem Description:</h1> + <p>Named paths are globally scoped, meaning a process located + in one jail can read and modify the content of POSIX shared + memory objects created by a process in another jail or the + host system.</p> + <h1>Impact:</h1> + <p>A malicious user that has access to a jailed system is + able to abuse shared memory by injecting malicious content + in the shared memory region. This memory region might be + executed by applications trusting the shared memory, like + Squid.</p> + <p>This issue could lead to a Denial of Service or local + privilege escalation.</p> + </body> + </description> + <references> + <cvename>CVE-2017-1087</cvename> + <freebsdsa>SA-17:09.shm</freebsdsa> + </references> + <dates> + <discovery>2017-11-15</discovery> + <entry>2017-12-06</entry> + </dates> + </vuln> + <vuln vid="34a3f9b5-dab3-11e7-b5af-a4badb2f4699"> <topic>FreeBSD -- Kernel data leak via ptrace(PT_LWPINFO)</topic> <affects> |