CWE-252: Unchecked Return Value | Causes and Fixes Skip to content

Security weakness

CWE-252 Unchecked Return Value

A base-level weakness that can lead to data, pages or code changed, downtime and lost sales and accounts and admin areas exposed. 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-252?

Unchecked Return Value: The product does not check the return value from a method or function.

Business impact

What CWE-252 could cost your business

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

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Unexpected State
  • DoS: Crash, Exit, or Restart

Availability

Downtime and lost sales

Crashes, slowdowns or exhausted resources can take your site, store or app offline.

  • Unexpected State
  • DoS: Crash, Exit, or Restart

Access Control

Accounts and admin areas exposed

Logins and permission checks can be bypassed, putting admin and customer accounts at risk.

  • Bypass Protection Mechanism

Free security check

Is CWE-252 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-252

Unchecked Return Value

The product does not check the return value from a method or function.

Weakness ID
CWE-252
Type
Base
Status
Draft
Likelihood of exploit
Low
Applies to
Python
Introduced during
Implementation

Prevention

How to fix CWE-252, phase by phase

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

  1. 01

    Implementation

    • Check the results of all functions that return a value and verify that the value is expected.
    • For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished [REF-1484].
    • Ensure that you account for all possible return values from the function.
    Show 1 more recommendation
    • When designing a function, make sure you return a value or throw an exception in case of an error.

Detection and evidence

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

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

Real vulnerabilities it caused

  • CVE-2020-17533Chain: unchecked return value (CWE-252) of some functions for policy enforcement leads to authorization bypass (CWE-862)
  • CVE-2020-6078Chain: The return value of a function returning a pointer is not checked for success (CWE-252) resulting in the later use of an uninitialized variable (CWE-456) and a null pointer dereference (CWE-476)
  • CVE-2019-15900Chain: sscanf() call is used to check if a username and group exists, but the return value of sscanf() call is not checked (CWE-252), causing an uninitialized variable to be checked (CWE-457), returning success to allow.
  • CVE-2007-3798Unchecked return value leads to resultant integer overflow and code execution.
  • CVE-2006-4447Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.
  • CVE-2006-2916Program does not check return value when invoking functions to drop privileges, which could leave users with higher privileges than expected by forcing those functions to fail.

How we fix it

From finding to fixed: how Codefreex closes CWE-252

  1. 01

    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. 02

    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. 03

    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. 04

    Keep it fixed

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

FAQ

CWE-252: FAQs

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

What is CWE-252?

CWE-252, “Unchecked Return Value”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product does not check the return value from a method or function.

How serious is CWE-252?

MITRE rates the likelihood of exploit as Low. It can affect availability, integrity, access control, with impacts such as unexpected state, varies by context, dos: crash, exit, or restart. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-252?

Check the results of all functions that return a value and verify that the value is expected. For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous.

Can Codefreex check my site for CWE-252?

Yes. A senior engineer reviews your site, store or app for CWE-252 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.

Which technologies does CWE-252 affect?

MITRE lists it as applicable to Python. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-252 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.