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 |
---|---|
https://www.freebsd.org/security/advisories/FreeBSD-SA-17:09.shm.asc | Vendor Advisory |
http://www.securitytracker.com/id/1039810 | Third Party Advisory VDB Entry |
http://www.securityfocus.com/bid/101867 | Third Party Advisory VDB Entry |
Configurations
Information
Published : 2017-11-16 12:29
Updated : 2019-10-02 17:03
NVD link : CVE-2017-1087
Mitre link : CVE-2017-1087
JSON object : View
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Products Affected
freebsd
- freebsd