CWE-508 Base Incomplete

Non-Replicating Malicious Code

This type of malicious code is designed to operate only on the specific system it initially infects. Unlike viruses or worms, it does not contain mechanisms to copy itself or spread to other devices…

Definition

What is CWE-508?

This type of malicious code is designed to operate only on the specific system it initially infects. Unlike viruses or worms, it does not contain mechanisms to copy itself or spread to other devices or networks.
Non-replicating malware, often called a 'one-shot' or 'targeted' attack, focuses all its impact on a single compromised host. Common examples include logic bombs that trigger on a specific date, spyware that steals data from one machine, or ransomware that encrypts only the local filesystem. Because it doesn't propagate, its discovery and containment are typically easier, but the damage to the initial target can be severe and deliberate. For developers, the key takeaway is that security defenses shouldn't focus solely on network perimeter controls. Strong host-based security—like application allow-listing, strict file integrity monitoring, and principle of least privilege enforcement—is critical to detect and stop these localized threats. Understanding this behavior helps in creating incident response plans that prioritize isolating the affected system without the added complexity of a widespread outbreak.
Real-world impact

Real-world CVEs caused by CWE-508

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

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

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

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-508

  • Operation Antivirus software can help mitigate known malicious code.
  • Installation Verify the integrity of the software that is being installed.
Detection signals

How to detect CWE-508

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.

Plexicus auto-fix

Plexicus auto-detects CWE-508 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-508?

This type of malicious code is designed to operate only on the specific system it initially infects. Unlike viruses or worms, it does not contain mechanisms to copy itself or spread to other devices or networks.

How serious is CWE-508?

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-508?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-508?

Antivirus software can help mitigate known malicious code. Verify the integrity of the software that is being installed.

How does Plexicus detect and fix CWE-508?

Plexicus's SAST engine matches the data-flow signature for CWE-508 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-508?

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

Related weaknesses

Weaknesses related to CWE-508

CWE-507 Parent

Trojan Horse

A Trojan Horse vulnerability occurs when software presents itself as legitimate and useful, but secretly contains malicious functionality…

CWE-509 Sibling

Replicating Malicious Code (Virus or Worm)

This weakness describes software that is vulnerable to infection by self-replicating malicious programs like viruses or worms. Once such…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.