The product performs a data query with a large number of joins and sub-queries on a large data table.
View on MITREThis issue can make the product perform more slowly. If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability. While the interpretation of "large data table" and "large number of joins or sub-queries" may vary for each product or developer, CISQ recommends a default of 1 million rows for a "large" data table, a default minimum of 5 joins, and a default minimum of 3 sub-queries.
No mitigation information available for this CWE.
No detection method information available for this CWE.
No examples or observed CVEs available for this CWE.
No relationship information available for this CWE.
CWE-1049: Excessive Data Query Operations in a Large Data Table is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product performs a data query with a large number of joins and sub-queries on a large data table. This issue can make the product perform more slowly. If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability. While the interpretation of "large data table" and "large number of joins or sub-queries" may vary for each product or developer, CISQ recommends a default of 1 million rows for a "large" data table, a default minimum of 5 joins, and a default minimum of 3 sub-queries.
If exploited, CWE-1049 (Excessive Data Query Operations in a Large Data Table) it can compromise Other, leading to outcomes such as Reduce Performance.
A CWE (Common Weakness Enumeration) like CWE-1049 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.