CWE-695: Use of Low-Level Functionality

BaseIncomplete

The product uses low-level functionality that is explicitly prohibited by the framework or specification under which the product is supposed to operate.

View on MITRE
Back to CWE Lookup

Extended Description

The use of low-level functionality can violate the specification in unexpected ways that effectively disable built-in protection mechanisms, introduce exploitable inconsistencies, or otherwise expose the functionality to attack.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect Use of Low-Level Functionality with Automated Static Analysis

Documented detection approaches include Automated Static Analysis; recorded impacts include Other; the entry maps to CAPEC-36. Use these source-defined anchors to turn CWE-695 into implementation, review, and verification checks for the affected component.

CWE-695: Use of Low-Level FunctionalityMITRE CWE

Prevent CWE-695 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-695, Use of Low-Level Functionality, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Triage CWE-695 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-695, Use of Low-Level Functionality, 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 CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-695

Apply MITRE's full root-cause mapping guidance when using CWE-695, Use of Low-Level Functionality. 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 GuidanceMITRE CWE

Validate CWE-695 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-695, Use of Low-Level Functionality. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-695: Use of Low-Level Functionality?+

CWE-695: Use of Low-Level Functionality is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product uses low-level functionality that is explicitly prohibited by the framework or specification under which the product is supposed to operate. The use of low-level functionality can violate the specification in unexpected ways that effectively disable built-in protection mechanisms, introduce exploitable inconsistencies, or otherwise expose the functionality to attack.

What are the security consequences of Use of Low-Level Functionality?+

If exploited, CWE-695 (Use of Low-Level Functionality) it can compromise Other, leading to outcomes such as Other.

Which programming languages are affected by Use of Low-Level Functionality?+

CWE-695 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-695 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.

Learn More

Advertisement