
Besides vertex positions, it also stores surface normal plus a UV coordinate that can be mapped to an external texture.


Echo "$srcPath: No such file or directory"Ĭp -R "$srcPath/meshmixer2.3/"* "$destPath/meshmixer" if thenįind ~/Documents/meshmixer/libraries/ default -type f -name *.prt -maxdepth 1 -exec cp -n ~/Documents/meshmixer/libraries/parts/user/My\ Parts/ \ īy placing a malicious symlink in "/tmp/Autodesk/meshmixer2.3", an attacker could cause files normal accessible by only the root user to be copied to "~/Documents/meshmixer" and have the permissions changed to "777", which allows the file(s) to be read by anyone.įurther, if a meshmixer install does not exist prior to installation, the user could create their own malicious file and place it in "/tmp/Autodesk/meshmixer2.3" and create a symlink for "~/Documents/meshmixer" that would cause their custom file to be place anywhere on the system (such as /Library/LaunchDaemons, which could spawn an application of their choosing as the root user), which results in privilege escalation to root with the possibility of code execution.At the start of a project, choose a file format that can comprehensively describe the design while suiting the intended applications and minimizing the need for file conversions.
