CWE-477: Use of Obsolete Function | Causes and Fixes Skip to content

Security weakness

CWE-477 Use of Obsolete Function

A base-level weakness that can lead to effects that depend on context. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is 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.

Business impact

What CWE-477 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Other

Effects that depend on context

The impact depends on where the weakness sits in your code and what it can reach.

  • Quality Degradation

Free security check

Is CWE-477 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines 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.

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.

Weakness ID
CWE-477
Type
Base
Status
Draft
Introduced during
Implementation

Prevention

How to fix CWE-477, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Requirements

    • Consider seriously the security implications of using an obsolete function. Consider using alternate functions.
  2. 02

    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.

Detection and evidence

How CWE-477 is found, and where it has hit

The testing methods MITRE recommends for finding it.

How it is detected

  • Automated Static Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Binary / Bytecode Quality Analysis Bytecode Weakness Analysis – including disassembler + source code weakness analysis
  • Manual Static Analysis – Binary or BytecodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Binary / Bytecode disassembler – then use manual analysis for vulnerabilities & anomalies
  • Dynamic Analysis with Manual Results InterpretationAccording to SOAR [REF-1479], the following detection techniques may be useful: Debugger
  • Manual Static Analysis – Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Manual Source Code Review (not inspections) Focused Manual Spotcheck – Focused manual analysis of source
  • Automated Static Analysis – Source CodeAccording to SOAR [REF-1479], the following detection techniques may be useful: Source Code Quality Analyzer Source code Weakness Analyzer Context-configured Source Code Weakness Analyzer

How we fix it

From finding to fixed: how Codefreex closes CWE-477

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-477: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-477?

CWE-477, “Use of Obsolete Function”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.

How serious is CWE-477?

It can affect other, with impacts such as quality degradation. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-477?

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. Consider seriously the security implications of using an obsolete function. Consider using alternate functions.

Can Codefreex check my site for CWE-477?

Yes. A senior engineer reviews your site, store or app for CWE-477 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-477 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.