python-rply CVE-2014-1938 Insecure Temporary File Creation Vulnerability
BID:65487
Info
python-rply CVE-2014-1938 Insecure Temporary File Creation Vulnerability
| Bugtraq ID: | 65487 |
| Class: | Design Error |
| CVE: |
CVE-2014-1938 |
| Remote: | No |
| Local: | Yes |
| Published: | Feb 04 2014 12:00AM |
| Updated: | Feb 04 2014 12:00AM |
| Credit: | Jakub Wilk |
| Vulnerable: |
python python-rply 0.7.1-1 |
| Not Vulnerable: | |
Discussion
python-rply CVE-2014-1938 Insecure Temporary File Creation Vulnerability
python-rply is prone to an insecure temporary file-creation vulnerability because it creates temporary files in an insecure manner.
An attacker with local access could potentially exploit this issue to perform symbolic-link attacks, overwriting arbitrary files in the context of the affected application. Other attacks may also be possible.
python-rply is prone to an insecure temporary file-creation vulnerability because it creates temporary files in an insecure manner.
An attacker with local access could potentially exploit this issue to perform symbolic-link attacks, overwriting arbitrary files in the context of the affected application. Other attacks may also be possible.
Exploit / POC
python-rply CVE-2014-1938 Insecure Temporary File Creation Vulnerability
An attacker uses readily available commands to exploit this issue.
An attacker uses readily available commands to exploit this issue.
Solution / Fix
python-rply CVE-2014-1938 Insecure Temporary File Creation Vulnerability
Solution:
Currently, we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution:
Currently, we are not aware of any vendor-supplied patches. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
References
python-rply CVE-2014-1938 Insecure Temporary File Creation Vulnerability
References:
References:
- Python Homepage (Python Software Foundation)
- python-rply: CVE-2014-1938: still uses /tmp insecurely (Jakub Wilk)