CWE · MITRE source
CWE-379Creation of Temporary File in Directory with Insecure Permissions
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
On some operating systems, the fact that the temporary file exists may be apparent to any user with sufficient privileges to access that directory. Since the file is visible, the application that is using the temporary file could be known. If one has access to list the processes on the system, the attacker has gained information about what the user is doing at that time. By correlating this with the applications the user is running, an attacker could potentially discover what a user's actions are. From this, higher levels of security could be breached.
Last updated: 04 July 2026 13:15 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 4 mapping(s) from 3 framework(s): ATT&CK 2 (partial) · OWASP-Web 1 (mostly) · STIG oracle linux 8 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2016-9486 | 5.5 | 7.8 | 0.0123 | 2018-07-13 |
CVE-2020-11979 | 5.5 | 7.5 | 0.0824 | 2020-10-01 |
CVE-2020-27216 | 5.5 | 7.0 | 0.0430 | 2020-10-23 |
CVE-2021-29428 | 5.5 | 8.8 | 0.0053 | 2021-04-13 |
CVE-2021-21100 | 5.5 | 7.8 | 0.0172 | 2021-04-15 |
CVE-2021-28613 | 5.5 | 7.4 | 0.0047 | 2021-09-27 |
CVE-2021-40708 | 5.5 | 7.3 | 0.0164 | 2021-09-29 |
CVE-2022-23950 | 5.5 | 7.5 | 0.0128 | 2022-09-21 |
CVE-2023-21611 | 5.5 | 7.8 | 0.0040 | 2023-01-18 |
CVE-2023-21612 | 5.5 | 7.8 | 0.0040 | 2023-01-18 |
CVE-2023-26396 | 5.5 | 7.8 | 0.0403 | 2023-04-12 |
CVE-2023-37243 | 5.5 | 7.8 | 0.0018 | 2023-10-31 |
CVE-2023-3972 | 5.5 | 7.8 | 0.0026 | 2023-11-01 |
CVE-2023-49797 | 5.5 | 8.8 | 0.0032 | 2023-12-09 |
CVE-2023-3181 | 5.5 | 7.8 | 0.0018 | 2024-01-25 |
CVE-2024-24693 UPD | 5.5 | 7.2 | 0.0018 | 2024-03-13 |
CVE-2023-6080 | 5.5 | 7.8 | 0.0022 | 2024-10-18 |
CVE-2024-9500 | 5.5 | 7.8 | 0.0019 | 2024-11-15 |
CVE-2024-9950 | 5.5 | 7.8 | 0.0030 | 2025-01-02 |
CVE-2025-21173 | 5.5 | 7.3 | 0.0122 | 2025-01-14 |
CVE-2025-27148 | 5.5 | 8.8 | 0.0023 | 2025-02-25 |
CVE-2025-32438 | 5.5 | 8.8 | 0.0015 | 2025-04-15 |
CVE-2025-10279 | 5.5 | 7.0 | 0.0022 | 2026-02-02 |
CVE-2026-54328 | 5.5 | 7.3 | 0.0011 | 2026-06-23 |
CVE-2013-1815 | 3.5 | 6.1 | 0.0046 | 2013-04-10 |