MATLAB Mex Local Command Execution Vulnerability
BID:6470
Info
MATLAB Mex Local Command Execution Vulnerability
| Bugtraq ID: | 6470 |
| Class: | Design Error |
| CVE: | |
| Remote: | No |
| Local: | Yes |
| Published: | Dec 23 2002 12:00AM |
| Updated: | Dec 23 2002 12:00AM |
| Credit: | Discovery of this issue is credited to Paul Szabo <[email protected]>. |
| Vulnerable: |
MathWorks MATLAB 6.5 |
| Not Vulnerable: | |
Discussion
MATLAB Mex Local Command Execution Vulnerability
MATLAB is prone to an issue which may allow local attackers to execute arbitrary commands with elevated privileges.
The MATLAB Mex script creates temporary files which are later executed to perform various actions. If an attacker can anticipate the name of a temporary file created by the Mex script, it is possible to create a malicious file in the place of the temporary file. The Mex script will then reportedly execute the malicious file.
This issue is compounded by the fact that Mex uses predictable names when creating temporary files, as described in BID 6469 "MATLAB Mex Insecure Temporary Files Vulnerability".
MATLAB is prone to an issue which may allow local attackers to execute arbitrary commands with elevated privileges.
The MATLAB Mex script creates temporary files which are later executed to perform various actions. If an attacker can anticipate the name of a temporary file created by the Mex script, it is possible to create a malicious file in the place of the temporary file. The Mex script will then reportedly execute the malicious file.
This issue is compounded by the fact that Mex uses predictable names when creating temporary files, as described in BID 6469 "MATLAB Mex Insecure Temporary Files Vulnerability".
Exploit / POC
MATLAB Mex Local Command Execution Vulnerability
No exploit is required.
No exploit is required.
Solution / Fix
MATLAB Mex Local Command Execution Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.