CWE-196: Unsigned to Signed Conversion Error

Definition

What is CWE-196?

This vulnerability occurs when a program takes an unsigned integer and converts it directly to a signed integer. If the original unsigned value is too large to fit within the signed type's positive range, the conversion results in an unexpected negative number, corrupting the data.

While less common than signed-to-unsigned errors, this conversion flaw is a critical enabler for buffer underwrite attacks. When a large unsigned value (like a size or index) becomes a large negative number after conversion, using it for array indexing or pointer arithmetic can shift memory access far below the intended buffer's start. This "underwrite" or "buffer underflow" grants attackers write access to sensitive stack memory, such as function return addresses or saved registers, which they typically cannot reach in a standard overflow. This vulnerability is particularly dangerous because it subverts common security assumptions. Developers often guard against overly large positive values but may not anticipate an index turning negative. The resulting out-of-bounds write can lead to arbitrary code execution, often with fewer detection hurdles than a classic buffer overflow, making it a subtle but powerful exploit precursor.

Real-world impact

Real-world CVEs caused by CWE-196

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

1
Identify a code path that handles untrusted input without validation.
2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
3
Deliver the payload through a normal request and observe the application's reaction.
4
Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo

// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}

Secure code example

Secure pseudo

// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Prevention checklist

How to prevent CWE-196

Requirements Choose a language which is not subject to these casting flaws.
Architecture and Design Design object accessor functions to implicitly check values for valid sizes. Ensure that all functions which will be used as a size are checked previous to use as a size. If the language permits, throw exceptions rather than using in-band errors.
Implementation Error check the return values of all functions. Be aware of implicit casts made, and use unsigned variables for sizes if at all possible.

Detection signals

How to detect CWE-196

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

CWE-196

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Frequently asked questions

What is CWE-196?

This vulnerability occurs when a program takes an unsigned integer and converts it directly to a signed integer. If the original unsigned value is too large to fit within the signed type's positive range, the conversion results in an unexpected negative number, corrupting the data.

How serious is CWE-196?

MITRE rates the likelihood of exploit as Medium — exploitation is realistic but typically requires specific conditions.

What languages or platforms are affected by CWE-196?

MITRE lists the following affected platforms: C, C++.

How can I prevent CWE-196?

Choose a language which is not subject to these casting flaws. Design object accessor functions to implicitly check values for valid sizes. Ensure that all functions which will be used as a size are checked previous to use as a size. If the language permits, throw exceptions rather than using in-band errors.

How does Plexicus detect and fix CWE-196?

Plexicus's SAST engine matches the data-flow signature for CWE-196 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-196?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/196.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-196

CWE-681 Parent

Ready to validate what matters?

Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.

Request AI Swarm Pentest

Unsigned to Signed Conversion Error

What is CWE-196?

Real-world CVEs caused by CWE-196

Step-by-step attacker path

Vulnerable pseudo

Secure pseudo

How to prevent CWE-196

How to detect CWE-196

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-196

Incorrect Conversion between Numeric Types

Integer Coercion Error

Unexpected Sign Extension

Signed to Unsigned Conversion Error

Numeric Truncation Error

Buffer Underwrite ('Buffer Underflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Further reading

Ready to validate what matters?

Check whether AI Swarm Pentest fits your environment.

Request received. Book the next step.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`