|
Blender Multiple Temporary File Security Issues
|
|
Secunia Advisory:
|
SA29842
|
|
|
Release Date:
|
2008-05-16
|
|
Popularity:
|
4,010 views
|
|
|
Critical:
|
Not critical
|
|
Impact:
|
Exposure of sensitive information
Privilege escalation
|
|
Where:
|
Local system
|
|
Solution Status:
|
Unpatched
|
|
| Software: | Blender 2.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Some security issues have been discovered in Blender, which can be exploited by malicious, local users to disclose potentially sensitive information and perform certain actions with escalated privileges.
The security issues are caused due to Blender handling temporary files in an insecure manner (e.g. creating "/tmp/quit.blend" when quitting Blender, using easy to guess file names and insecure file permissions to store temporary render frames, and insecure file permission when auto saving files). This can be exploited to e.g. conduct symlink attacks and overwrite arbitrary files with the permissions of the user running Blender or disclose potentially sensitive information.
The security issues are confirmed in version 2.45 on a Linux system. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
