...
| Wiki Markup |
|---|
A recently identified bug manifests in JRE and JDK version 6.0 and prior, wherein an attacker can predict the names of the temporary files and as a result write malicious JAR files via unknown vectors \[[CVE 2008|AA. JavaBibliography#CVE References#CVE 08]\]. Denial of Service attacks are also possible if unclaimed temporary resources cause rapid disk space exhaustion \[[Secunia Advisory 20132|http://secunia.com/advisories/20132/]\]. |
...
| Wiki Markup |
|---|
Exclusive access grants unrestricted file access to the locking process while denying access to all other processes and eliminates the potential for a race condition on the locked region. Files, or regions of files, can be locked to prevent two processes from concurrent access. The {{java.nio.channels.FileLock}} class facilitates file locking. According to the Java API \[[API 2006|AA. JavaBibliography#API References#API 06]\] documentation |
A file lock is either exclusive or shared. A shared lock prevents other concurrently-running programs from acquiring an overlapping exclusive lock, but does allow them to acquire overlapping shared locks. An exclusive lock prevents other programs from acquiring an overlapping lock of either type. Once it is released, a lock has no further effect on the locks that may be acquired by other programs.
...
| Wiki Markup |
|---|
"Whether or not a lock actually prevents another program from accessing the content of the locked region is system-dependent and consequently unspecified" \[[API 2006|AA. Java References#APIBibliography#API 06]\]. Microsoft Windows uses a file-locking mechanism called mandatory locking because every process attempting access to a locked file region is subject to the restriction. Linux implements mandatory locks and advisory locks. An advisory lock is not enforced by the operating system, which severely diminishes its value from a security perspective. Unfortunately, the mandatory file lock in Linux is also largely impractical for the following reasons: |
...
| Wiki Markup |
|---|
According to the Java API \[[API 2006|AA. Java References#APIBibliography#API 06]\] Class {{File}}, method {{deleteOnExit()}} documentation: |
...
| Wiki Markup |
|---|
\[[API 2006|AA. Java References#APIBibliography#API 06]\] Class File, methods {{createTempFile}}, {{delete}}, {{deleteOnExit}} \[[Darwin 2004|AA. JavaBibliography#Darwin References#Darwin 04]\] 11.5 Creating a Transient File \[[SDN 2008|AA. JavaBibliography#SDN References#SDN 08]\] Bug IDs: 4171239, 4405521, 4635827, 4631820 \[[Secunia 2008|AA. Java References#SecuniaBibliography#Secunia 08]\] [Secunia Advisory 20132|http://secunia.com/advisories/20132/] \[[CVE 2008|AA. Java References#CVEBibliography#CVE 08]\] [CVE-2008-5354|http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5354] \[[MITRE 2009|AA. Java References#MITREBibliography#MITRE 09]\] [CWE ID 459 |http://cwe.mitre.org/data/definitions/459.html] "Incomplete Cleanup", [CWE ID 377|http://cwe.mitre.org/data/definitions/377.html] "Insecure Temporary File" |
...