CWE-1073: Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect imprecise mappings involving CWE-1073

Review mappings to CWE-1073, Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses, with MITRE's mapping and navigation criteria. Flag any selection that points to a View or Category, remains at a higher abstraction than the available evidence supports, or ignores relevant parent, child, peer, and alternative entries. Treat those findings as mapping-quality defects, correct them before publication, and retain the comparison trail for repeatable audits.

CWE Mapping and Navigation Guidance — MITRE CWE

Prevent CWE-1073 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-1073, Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses, 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 Framework — National Institute of Standards and Technology

Triage CWE-1073 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1073, Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses, 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

Use MITRE taxonomy anchors to review Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses

Recorded impacts include Reduce Performance; related weaknesses include CWE-405; applicable implementation contexts include SQL, and Database Server. Use these source-defined anchors to turn CWE-1073 into implementation, review, and verification checks for the affected component.

CWE-1073: Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses — MITRE CWE

Validate CWE-1073 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1073, Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses. 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-1073: Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses?+

CWE-1073: Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities. While the interpretation of "large number of data accesses/queries" may vary for each product or developer, CISQ recommends a default maximum of 2 data accesses per function/method.

What are the security consequences of Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses?+

If exploited, CWE-1073 (Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses) it can compromise Other, leading to outcomes such as Reduce Performance.

Which programming languages are affected by Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses?+

CWE-1073 commonly affects SQL. 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-1073 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-1073: Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses