CWE-512: Spyware

Extended Description

"Spyware" is a commonly used term with many definitions and interpretations. In general, it is meant to refer to products that collect information or install functionality that human users might not allow if they were fully aware of the actions being taken by the software. For example, a user might expect that tax software would collect a social security number and include it when filing a tax return, but that same user would not expect gaming software to obtain the social security number from that tax software's data.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-512 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-512, Spyware, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Spyware during Operation

MITRE associates mitigation with Operation, and Installation; recorded impacts include Read Application Data; related weaknesses include CWE-506. Use these source-defined anchors to turn CWE-512 into implementation, review, and verification checks for the affected component.

CWE-512: Spyware — MITRE CWE

Triage CWE-512 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-512, Spyware, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-512

Apply MITRE's full root-cause mapping guidance when using CWE-512, Spyware. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-512 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-512, Spyware. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-512: Spyware?+

CWE-512: Spyware is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product collects personally identifiable information about a human user or the user's activities, but the product accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the product. "Spyware" is a commonly used term with many definitions and interpretations. In general, it is meant to refer to products that collect information or install functionality that human users might not allow if they were fully aware of the actions being taken by the software. For example, a user might expect that tax software would collect a social security number and include it when filing a tax return, but that same user would not expect gaming software to obtain the social security number from that tax software's data.

What are the security consequences of Spyware?+

If exploited, CWE-512 (Spyware) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Spyware?+

Recommended mitigations for CWE-512 include: Use spyware detection and removal software. Always verify the integrity of the product that is being installed.

Which programming languages are affected by Spyware?+

CWE-512 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-512 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-512: Spyware

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Phase

Description

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses