Docker versions 1.3.0 through 1.3.1 allowed security options to be applied to images, allowing images to modify the default run profile of containers executing these images. This vulnerability could allow a malicious image creator to loosen the restrictions applied to a container"s processes, potentially facilitating a break-out. The Docker engine, up to and including version 1.3.1, was vulnerable to extracting files to arbitrary paths on the host during "docker pull" and "docker load" operations. This was caused by symlink and hardlink traversals present in Docker"s image extraction. This vulnerability could be leveraged to perform remote code execution and privilege escalation