BaseDraft

CWE-477Use of Obsolete Function

Category: other

Description

The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.

Common consequences· 1

  • Other — Quality Degradation

Potential mitigations· 2

  • [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.

References

  1. https://cwe.mitre.org/data/definitions/477.html

(incoming)7

TypeTargetConfidenceTier
VulnerabilityCVE-2025-49212cve-2025-492120%live
VulnerabilityCVE-2025-49213cve-2025-492130%live
VulnerabilityCVE-2025-49214cve-2025-492140%live
VulnerabilityCVE-2025-49216cve-2025-492160%live
VulnerabilityCVE-2025-49217cve-2025-492170%live
VulnerabilityCVE-2025-49219cve-2025-492190%live
VulnerabilityCVE-2025-49220cve-2025-492200%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Use of Prohibited Code
CWE
Use of Function with Inconsistent Implementations
CWE
Use of Potentially Dangerous Function
CWE
Insufficient Use of Symbolic Constants
CWE
Inaccurate Source Code Comments
CWE
Incorrect Provision of Specified Functionality
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.