In FreeBSD 10.x before 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24 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. As a result, 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. This issue could lead to a Denial of Service or local privilege escalation.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/101867 | Third Party Advisory VDB Entry |
http://www.securitytracker.com/id/1039810 | Third Party Advisory VDB Entry |
https://www.freebsd.org/security/advisories/FreeBSD-SA-17:09.shm.asc | Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: freebsd
Published: 2017-11-15T00:00:00
Updated: 2017-11-17T10:57:01
Reserved: 2016-11-30T00:00:00
Link: CVE-2017-1087
JSON object: View
NVD Information
Status : Analyzed
Published: 2017-11-16T20:29:00.237
Modified: 2019-10-03T00:03:26.223
Link: CVE-2017-1087
JSON object: View
Redhat Information
No data.
CWE