VNX-475 – Undefined Behavior for Input to API

Overview

VNX-475 maps to CWE-475: Undefined Behavior for Input to API. Detects source patterns associated with CWE-475 (Undefined Behavior for Input to API). Each finding should be manually reviewed for exploitability in context.

Severity: Low | CWE: CWE-475 | Languages: c

Why This Matters

This weakness class (Undefined Behavior for Input to API) creates a concrete exploit surface: the rule searches for the concrete source-level patterns most commonly associated with CWE-475 and surfaces them for review. Each finding should be evaluated in context — the rule catches the pattern, not the context.

What Gets Flagged

// FLAGGED: contains 'INT_MAX + 1' pattern
INT_MAX + 1

Remediation

  1. Review each flagged line and determine whether the pattern represents a real instance of CWE-475 or a false positive.
  2. Replace the flagged construct with a documented safe alternative appropriate to your language and framework.
  3. For confirmed false positives, add a # vulnetix-ignore: VNX-475 comment on the line.
  4. Ensure equivalent test coverage exists to prevent regression.

References