CWE-477: Use of Obsolete Function
Base
The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.
As programming languages evolve, functions occasionally become obsolete due to: Advances in the language Improved understanding of how operations should be performed effectively and securely Changes in the conventions that govern certain operations Functions that are removed are usually replaced by newer counterparts that perform the same task in some different and hopefully improved way.
Consequences
- Other: Quality Degradation
How to prevent it
- Implementation: Refer to the documentation for the obsolete function in order to determine why it is deprecated or obsolete and to learn about alternative ways to achieve the same functionality.
- Requirements: Consider seriously the security implications of using an obsolete function. Consider using alternate functions.
Recent advisories
- GO-2022-0576 — Insecure plugin handling in Mattermost
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