CWE-544: Missing Standardized Error Handling Mechanism
Base
The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.
If the product handles error messages individually, on a one-by-one basis, this is likely to result in inconsistent error handling. The causes of errors may be lost. Also, detailed information about the causes of an error may be unintentionally returned to the user.
Consequences
- Integrity, Other: Quality Degradation, Unexpected State, Varies by Context
How to prevent it
- Architecture and Design: define a strategy for handling errors of different severities, such as fatal errors versus basic log events. Use or create built-in language features, or an external package, that provides an easy-to-use API and define coding standards for the detection and handling of errors.
Recent advisories
- GHSA-9r6p-hg4g-5gxp — Microweber missing standardized error handling mechanism
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