CWE-378: Creation of Temporary File With Insecure Skip to content

Security weakness

CWE-378 Creation of Temporary File With Insecure Permissions

A base-level weakness that can lead to private data exposed, data, pages or code changed and people reach what they should not. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-378?

Creation of Temporary File With Insecure Permissions: Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

Business impact

What CWE-378 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Read Application Data

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Other

Authorization

People reach what they should not

Users can open records, pages or actions that belong to other users or to admins.

  • Other

Free security check

Is CWE-378 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-378

Creation of Temporary File With Insecure Permissions

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

Weakness ID
CWE-378
Type
Base
Status
Draft
Likelihood of exploit
High
Introduced during
Implementation

Prevention

How to fix CWE-378, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Requirements

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

    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.

Detection and evidence

How CWE-378 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Static AnalysisAutomated 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.

Real vulnerabilities it caused

  • CVE-2022-24823A network application framework uses the Java function createTempFile(), which will create a file that is readable by other local users of the system
  • CVE-2022-41954A library uses the Java File.createTempFile() method which creates a file with "-rw-r–r–" default permissions on Unix-like operating systems

How we fix it

From finding to fixed: how Codefreex closes CWE-378

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-378: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-378?

CWE-378, “Creation of Temporary File With Insecure Permissions”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

How serious is CWE-378?

MITRE rates the likelihood of exploit as High. It can affect confidentiality, authorization, other, integrity, with impacts such as read application data, other. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-378?

Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible. 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.

Can Codefreex check my site for CWE-378?

Yes. A senior engineer reviews your site, store or app for CWE-378 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-378 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.