Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
Deprecated by MITRE
This CWE entry has been deprecated by MITRE. It is kept here for reference and backward compatibility with older links. Browse the active weaknesses catalogue for current guidance.
CWE-132 Base Deprecated
DEPRECATED: Miscalculated Null Termination
This entry has been deprecated and merged into CWE-170 (Improper Null Termination). It was originally created as a duplicate, and all relevant information has been consolidated under CWE-170 for…
Definition
What is CWE-132?
This entry has been deprecated and merged into CWE-170 (Improper Null Termination). It was originally created as a duplicate, and all relevant information has been consolidated under CWE-170 for clearer vulnerability tracking.
CWE-132 was deprecated because it described the same core issue as CWE-170: problems arising when software incorrectly calculates buffer sizes or termination points for null-terminated strings. This often happens when developers manually manage string buffers without using safe functions, leading to off-by-one errors that can create non-terminated strings. These non-terminated strings then cause unexpected behavior when processed by functions that expect proper null termination.
As a developer, you should now reference CWE-170 for comprehensive guidance on preventing null termination errors. Focus on using secure string handling functions from modern libraries, always validating buffer sizes, and avoiding manual character-by-character buffer manipulation. The consolidation into a single CWE entry helps streamline security education and ensures you're working with the most current and complete vulnerability information.
Real-world impact
Real-world CVEs caused by CWE-132
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.
// 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-132
- Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
- Implementation Validate input at trust boundaries; use allowlists, not denylists.
- Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
- Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
- Operation Monitor logs for the runtime signals listed in the next section.
Detection signals
How to detect CWE-132
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
CWE-132
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.
Frequently asked questions What is CWE-132?
How serious is CWE-132?
What languages or platforms are affected by CWE-132?
How can I prevent CWE-132?
How does Plexicus detect and fix CWE-132?
Where can I learn more about CWE-132?
Frequently asked questions
What is CWE-132?
This entry has been deprecated and merged into CWE-170 (Improper Null Termination). It was originally created as a duplicate, and all relevant information has been consolidated under CWE-170 for clearer vulnerability tracking.
How serious is CWE-132?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-132?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-132?
Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.
How does Plexicus detect and fix CWE-132?
Plexicus's SAST engine matches the data-flow signature for CWE-132 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-132?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/132.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-132
No related weaknesses indexed for this CWE.
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.