Weakness · High

CWE-378: Creation of Temporary File With Insecure Permissions

What it is

Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

Likelihood of exploit: HighMITRE CWE 4.19.1

Severity (our rating)
High
Likelihood of exploit
High
Introduced during
Implementation
Exploited in the wild
No CVE in CISA's catalog

What an attacker can do

  • Read Application Data (Confidentiality)
  • Other (Authorization, Other, Integrity)

How to prevent it

Requirements

  • Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.

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 that owns the file.
  • 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.

How to find it

  • Automated Static Analysis. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

CWE-378 on MITRE's CWE site

H2 Security

Found it in your code?

We review where it appears, fix it with your team, and check it was not already used against you.

Talk to our team

T Academy

Stop writing it in the first place

Learn to build software and systems without weaknesses like this one, with practice on real hosts in your browser, every objective checked on the machine.

Start free

Source: MITRE Common Weakness Enumeration, CWE version 4.19.1. CWE is a trademark of The MITRE Corporation.