Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-512 Base Incomplete
Spyware
Spyware is software that secretly gathers personal information about a user or their activities. It does this by accessing data from other sources on the system, without the user's direct input or…
Definition
What is CWE-512?
Spyware is software that secretly gathers personal information about a user or their activities. It does this by accessing data from other sources on the system, without the user's direct input or explicit consent.
Spyware operates by collecting sensitive data—like browsing habits, personal identifiers, or system information—from other applications or system resources without transparently asking for permission. This creates a security risk because users are unaware of what information is being harvested or where it is being sent, violating the principle of informed consent.
For developers, the core issue is a failure of data boundary enforcement. Software should only collect data that is directly relevant to its function and must do so with clear, upfront user approval. A tax application legitimately needs a Social Security Number, but a game secretly pulling that same data from the tax software's files is a clear abuse. Building ethical software requires explicit user prompts for sensitive data and strict isolation from unrelated system resources.
Real-world impact
Real-world CVEs caused by CWE-512
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-512
- Operation Use spyware detection and removal software.
- Installation Always verify the integrity of the product that is being installed.
Detection signals
How to detect CWE-512
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-512
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-512?
How serious is CWE-512?
What languages or platforms are affected by CWE-512?
How can I prevent CWE-512?
How does Plexicus detect and fix CWE-512?
Where can I learn more about CWE-512?
Frequently asked questions
What is CWE-512?
Spyware is software that secretly gathers personal information about a user or their activities. It does this by accessing data from other sources on the system, without the user's direct input or explicit consent.
How serious is CWE-512?
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-512?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-512?
Use spyware detection and removal software. Always verify the integrity of the product that is being installed.
How does Plexicus detect and fix CWE-512?
Plexicus's SAST engine matches the data-flow signature for CWE-512 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-512?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/512.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-512
CWE-506 Parent
Embedded Malicious Code
This vulnerability occurs when an application or codebase contains intentionally harmful code inserted by a developer or third party.
CWE-507 Sibling
Trojan Horse
A Trojan Horse vulnerability occurs when software presents itself as legitimate and useful, but secretly contains malicious functionality…
CWE-510 Sibling
Trapdoor
A trapdoor, often called a backdoor, is a hidden piece of code intentionally placed within software. It activates in response to a…
CWE-511 Sibling
Logic/Time Bomb
A logic or time bomb is malicious code intentionally placed within software to trigger harmful actions when a specific condition is met or…
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.