Creation of Temporary File With Insecure Permissions |
Weakness ID: 378 (Weakness Base) | Status: Draft |
Description Summary
Scope | Effect |
---|---|
Confidentiality | If the temporary file can be read, by the attacker, sensitive information may be in that file which could be revealed. |
Authorization | If that file can be written to by the attacker, the file might be moved into a place to which the attacker does not have access. This will allow the attacker to gain selective resource access-control privileges. |
Integrity | Depending on the data stored in the temporary file, there is the potential for an attacker to gain an additional input vector which is trusted as non-malicious. It may be possible to make arbitrary changes to data structures, user information, or even process ownership. |
Example 1
The temp file created in the above code is always readable and writable by all users.
This temp file is readable by all users.
Tempfile creation should be done in a safe way. To be safe, the temp file function should open up the temp file with appropriate access control. The temp file function should also retain this quality, while being resistant to race conditions. |
Requirements specification: Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible. |
Phase: Implementation Ensure that you use proper file permissions. This can be achieved by using a safe temp file function. Temporary files should be writable and readable only by the process which own the file. |
Phase: Implementation Randomize temporary file names. This can also be achieved by using a safe temp-file function. This will ensure that temporary files will not be created in predictable places. |
Nature | Type | ID | Name | View(s) this relationship pertains to |
---|---|---|---|---|
ChildOf | Category | 376 | Temporary File Issues | Development Concepts (primary)699 |
ChildOf | Weakness Base | 377 | Insecure Temporary File | Research Concepts (primary)1000 |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
CLASP | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Eric Dalci | Cigital | External | |
updated Time of Introduction | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Common Consequences, Relationships, Other Notes, Taxonomy Mappings | ||||
2009-10-29 | CWE Content Team | MITRE | Internal | |
updated Common Consequences, Other Notes | ||||
Previous Entry Names | ||||
Change Date | Previous Entry Name | |||
2008-04-11 | Improper Temporary File Opening | |||