CWE-277 Insecure Inherited Permissions: Umask and Temp Files
CWE-277 is when objects a program creates inherit insecure permissions, such as the user's umask on temp files. Learn how to set modes on purpose.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
CWE-277 is when objects a program creates inherit insecure permissions, such as the user's umask on temp files. Learn how to set modes on purpose.
CWE-276 is software that installs files others can modify. See how world-writable defaults arise in installers and images, how to audit them, and how to fix them.
CWE-274 is what happens when a program does not cope with lacking the privileges it needs. Learn how the failure path becomes a weakness and how to handle it.
CWE-273 is dropping privileges without confirming it worked. Unchecked setuid return values leave programs running as root. See the pattern and fix.
CWE-272 means keeping elevated privilege longer than needed. Learn the drop-after-use pattern for chroot and other privileged calls, with code in C.
CWE-271 is handing a resource to an unprivileged actor without lowering your own rights first. Setuid examples, a C pattern, and how to test it.
CWE-270 is mismanaging privileges when moving between contexts with different trust, from browser zones to callbacks. Learn the pattern and fixes.
Strip one dot-dot-slash and the attacker sends two. How CWE-27 defeats single-removal filters and start-of-string checks, with a fix that does not depend on either.
CWE-269 is the parent of many privilege bugs: assigning, modifying, tracking, or checking privileges wrongly. A guide to the pattern, real CVEs, and a fix list.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.