CWE-267 Privilege Defined With Unsafe Actions: Dangerous Roles
CWE-267 is a role or capability that can do unsafe things even when given to the right person. Learn to scope privileges to what they need.
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-267 is a role or capability that can do unsafe things even when given to the right person. Learn to scope privileges to what they need.
CWE-266 is giving an actor a privilege it should not have. Real examples include untrusted users in the wheel group. Here is how to spot and prevent it.
CWE-263 covers password aging policies where the expiry window is too long. Here is why that matters, why shorter is not automatically better, and what to do.
CWE-262 flags products with no password aging mechanism. MITRE also notes why rotation has fallen out of favor, and where it is still required.
Obscuring a password with base64 or a similar encoding protects nothing. CWE-261 covers why and what to do instead.
A password in a config file is readable by anyone who can read the file, including backups and repos. CWE-260 explains the risk and safer alternatives.
A path that starts clean and climbs out later slips past prefix checks. How CWE-26 works, with real cases from MITRE and a safe resolve-then-compare fix.
A password baked into code or firmware is shared by every copy and almost impossible to change. CWE-259 covers both variants and how to avoid them.
A blank password in a config file is an open door that looks like a lock. CWE-258 covers how it gets there and how to catch it.
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.