Weakness (CWE)
CWE-477: Use of Obsolete Function
The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.
More detail
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.
How to prevent it (2 mitigations)
-
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.
Source: MITRE CWE-477
2 results · Clear filters · Feed
-
Medium 5.3
Use of vulnerable Resource Owner Password Credentials flow
The OAuth grant type Resource Owner Password Credentials (ROPC) flow is still used by the werbservices used by the WebVue, WebScheduler, TouchVue and Snapvue features of PcVue in version 12.0.0 through 16.3.3 included despite being deprecated. It might allow …
-
Medium 4.7
Authorized users are allowed to install old plugin versions from the Marketplace
Mattermost version 6.4.x and earlier fails to properly check the plugin version when a plugin is installed from the Marketplace, which allows an authenticated and an authorized user to install and exploit an old plugin version from the Marketplace which might…