CWE-230: Improper Handling of Missing Values

Code Examples & CVEs

Demonstrative Examples

This Android application has registered to handle a URL when sent an intent:

The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.

BadJava

...                      IntentFilter filter = new IntentFilter("com.example.URLHandler.openURL");MyReceiver receiver = new MyReceiver();registerReceiver(receiver, filter);                      ...                                            public class UrlHandlerReceiver extends BroadcastReceiver {                         @Overridepublic void onReceive(Context context, Intent intent) {                               if("com.example.URLHandler.openURL".equals(intent.getAction())) {String URL = intent.getStringExtra("URLToOpen");int length = URL.length();                                                                    ...                                  }                            }                      }

Observed CVE Examples (4)

CVE-2002-0422

Blank Host header triggers resultant infoleak.

View Details

CVE-2000-1006

Blank "charset" attribute in MIME header triggers crash.

View Details

CVE-2004-1504

Blank parameter causes external error infoleak.

View Details

CVE-2005-2053

Blank parameter causes external error infoleak.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-230 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-230, Improper Handling of Missing Values, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Make elimination of CWE-230 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-230, Improper Handling of Missing Values. Put the weakness in the product threat model and security roadmap, fund class-level design and platform changes, prefer safe defaults and reusable guardrails, and publish measurable progress. Do not transfer the primary burden to customer configuration when the manufacturer can remove or contain the root cause in the product.

Shifting the Balance of Cybersecurity Risk: Secure by Design Software — Cybersecurity and Infrastructure Security Agency

Connect Improper Handling of Missing Values to documented attack evidence

Recorded impacts include Unexpected State; observed examples include CVE-2002-0422, CVE-2000-1006, and CVE-2004-1504; related weaknesses include CWE-229. Use these source-defined anchors to turn CWE-230 into implementation, review, and verification checks for the affected component.

CWE-230: Improper Handling of Missing Values — MITRE CWE

Apply precise root-cause mapping to CWE-230

Apply MITRE's full root-cause mapping guidance when using CWE-230, Improper Handling of Missing Values. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-230 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-230, Improper Handling of Missing Values. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-230: Improper Handling of Missing Values?+

CWE-230: Improper Handling of Missing Values is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not handle or incorrectly handles when a parameter, field, or argument name is specified, but the associated value is missing, i.e. it is empty, blank, or null.

What are the security consequences of Improper Handling of Missing Values?+

If exploited, CWE-230 (Improper Handling of Missing Values) it can compromise Integrity, leading to outcomes such as Unexpected State.

Which programming languages are affected by Improper Handling of Missing Values?+

CWE-230 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Handling of Missing Values?+

MITRE documents real CVEs mapped to CWE-230, including CVE-2002-0422, CVE-2000-1006, CVE-2004-1504 and CVE-2005-2053. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-230 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-230: Improper Handling of Missing Values

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (4)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-230 with SSDF evidence

Make elimination of CWE-230 a product outcome

Connect Improper Handling of Missing Values to documented attack evidence

Apply precise root-cause mapping to CWE-230

Validate CWE-230 with root-cause mapping checks

Frequently Asked Questions

Learn More