Skip to content

CWE-280: Improper Handling of Insufficient Permissions or Privileges

Base

The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.

Consequences

  • Other: Other, Alter Execution Logic

How to prevent it

  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Implementation: Always check to see if you have successfully accessed a resource or system functionality, and use proper error handling if it is unsuccessful. Do this even when you are operating in a highly privileged mode, because errors or environmental conditions might still cause a failure. For example, environments with highly granular permissions/privilege models, such as Windows or Linux capabilities, can cause unexpected failures.

Recent advisories

  • GHSA-jm5p-837g-rv8g — Wagtail: Improper restriction handling on Page translation API endpoint
  • GHSA-x5cx-w6p2-mxf2 — Wagtail: Improper permission handling when copying snippets
  • GHSA-c2xx-cjmh-9q8f — Wagtail: Improper restriction handling on descendant collections in Documents and Images API
  • GHSA-92hv-j533-69wc — Wagtail: Identification of documents by SHA1 hash
  • GHSA-3vrh-m9w7-v94f — Wagtail: Improper restriction handling on Pages admin API
  • GHSA-fj8v-hjwv-qm88 — Gitea: Fork-PR Actions task can read a third private repository via the collaborative-owner branch (missing fork-PR guard)
  • GHSA-8634-mr4j-r72c — Wagtail: Pages translations can be created without page permissions when using simple_translation
  • GHSA-r6p4-grq7-xm4m — Wagtail: Improper permission handling in image preview
  • GHSA-h54r-xq46-qwqm — Wagtail: Improper restriction handling on Documents and Images chosen endpoints
  • GHSA-33j3-g875-37rp — Keycloak Vulnerable to Improper Handling of Insufficient Permissions or Privilege
  • GHSA-67rv-mg8q-5pf3 — Wagtail has improper permission handling when copying pages
  • GHSA-p5gm-92h4-6pv6 — Wagtail has improper restriction handling on Documents and Images API
  • GHSA-pwm3-7fv4-g6xx — Wagtail has improper permission handling when deleting form submissions
  • GHSA-c4mr-889m-vgf6 — Wagtail has improper permission handling when viewing page history
  • GHSA-c6wj-9vcj-75pj — Wagtail has improper permission handling when comparing revisions

All advisories for CWE-280

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor