ID string | Name string | Abstraction string | Structure string | Status string | Diagram string | Description string | ExtendedDescription string | LikelihoodOfExploit string | RelatedWeaknesses list | ApplicablePlatforms list | ModesOfIntroduction list | CommonConsequences list | DetectionMethods list | PotentialMitigations list | DemonstrativeExamples list | ObservedExamples list | TaxonomyMappings list | RelatedAttackPatterns list | References list | Notes list | ContentHistory list | MappingNotes_Usage string | MappingNotes_Rationale string | MappingNotes_Comments string | MappingNotes_Reasons list | MappingNotes_Suggestions list | WeaknessOrdinalities list | AlternateTerms list | AffectedResources list | FunctionalAreas list | BackgroundDetails list | NumPaths int64 | Paths list | Children list |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
20 | Improper Input Validation | Class | Simple | Stable | /data/images/CWE-20-Diagram.png | The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. |
Input validation is a frequently-used technique for checking potentially dangerous inputs in order to ensure that the inputs are safe for processing within the code, or when communicating with other components.
Input can consist of:
- raw data - strings, numbers, parameters, file contents, etc.
- metadata - information about the raw data, such as headers or size
Data can be simple or structured. Structured data can be composed of many nested layers, composed of combinations of metadata and raw data, with other simple or structured data.
Many properties of raw data or metadata may need to be validated upon entry into the code, such as:
- specified quantities such as size, length, frequency, price, rate, number of operations, time, etc.
- implied or derived quantities, such as the actual size of a file instead of a specified size
- indexes, offsets, or positions into more complex data structures
- symbolic keys or other elements into hash tables, associative arrays, etc.
- well-formedness, i.e. syntactic correctness - compliance with expected syntax
- lexical token correctness - compliance with rules for what is treated as a token
- specified or derived type - the actual type of the input (or what the input appears to be)
- consistency - between individual data elements, between raw data and metadata, between references, etc.
- conformance to domain-specific rules, e.g. business logic
- equivalence - ensuring that equivalent inputs are treated the same
- authenticity, ownership, or other attestations about the input, e.g. a cryptographic signature to prove the source of the data
Implied or derived properties of data must often be calculated or inferred by the code itself. Errors in deriving properties may be considered a contributing factor to improper input validation. | High | [] | [
{
"Class": "Not Language-Specific",
"Name": null,
"Prevalence": "Often",
"Type": "Language"
}
] | [
{
"Note": null,
"Phase": "Architecture and Design"
},
{
"Note": "\n\nREALIZATION: This weakness is caused during implementation of an architectural security tactic.\n\n\nIf a programmer believes that an attacker cannot modify certain inputs, then the programmer might not perform any input validation... | [
{
"Impact": [
"DoS: Crash, Exit, or Restart",
"DoS: Resource Consumption (CPU)",
"DoS: Resource Consumption (Memory)"
],
"Likelihood": null,
"Note": "An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excess... | [
{
"Description": "\n\nSome instances of improper input validation can be detected using automated static analysis.\n\n\nA static analysis tool might allow the user to specify which application-specific methods or functions perform input validation; the tool might also have built-in knowledge of validation frame... | [
{
"Description": "Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build \"recognizers\" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data repres... | [
{
"Entries": [
{
"BodyText": null,
"ExampleCode": null,
"IntroText": "This example demonstrates a shopping interaction in which the user is free to specify the quantity of items to be purchased and a total is calculated.",
"Language": null,
"Nature": null,
"... | [
{
"Description": "Large language model (LLM) management tool does not validate the format of a digest value (CWE-1287) from a private, untrusted model registry, enabling relative path traversal (CWE-23), a.k.a. Probllama",
"Link": "https://www.cve.org/CVERecord?id=CVE-2024-37032",
"Reference": "CVE-2024... | [
{
"EntryID": null,
"EntryName": "Input validation and representation",
"MappingFit": null,
"TaxonomyName": "7 Pernicious Kingdoms"
},
{
"EntryID": "A1",
"EntryName": "Unvalidated Input",
"MappingFit": "CWE More Specific",
"TaxonomyName": "OWASP Top Ten 2004"
},
{
"EntryID... | [
"10",
"101",
"104",
"108",
"109",
"110",
"120",
"13",
"135",
"136",
"14",
"153",
"182",
"209",
"22",
"23",
"230",
"231",
"24",
"250",
"261",
"267",
"28",
"3",
"31",
"42",
"43",
"45",
"46",
"47",
"473",
"52",
"53",
"588",
"63",
"64",
"664",
"6... | [
{
"Authors": [
"Katrina Tsipenyuk",
"Brian Chess",
"Gary McGraw"
],
"Edition": null,
"ExternalReferenceID": "REF-6",
"Publication": "NIST Workshop on Software Security Assurance Tools Techniques and Metrics",
"PublicationDay": "07",
"PublicationMonth": "11",
"Public... | [
{
"Note": "\n\nCWE-116 and CWE-20 have a close association because, depending on the nature of the structured message, proper input validation can indirectly prevent special characters from changing the meaning of a structured message. For example, by validating that a numeric ID field should only contain the 0... | [
{
"ContributionComment": null,
"ContributionDate": null,
"ContributionName": null,
"ContributionOrganization": null,
"ContributionReleaseDate": null,
"ContributionType": null,
"ContributionVersion": null,
"Date": null,
"ModificationComment": null,
"ModificationDate": null,
... | Discouraged | CWE-20 is commonly misused in low-information vulnerability reports when lower-level CWEs could be used instead, or when more details about the vulnerability are available [REF-1287]. It is not useful for trend analysis. It is also a level-1 Class (i.e., a child of a Pillar). Finally, it is often used when the root cause issue is related to how input is incorrectly transformed, instead of "validated" to be correct as-is. | Within CWE, the "input validation" term focuses on the act of checking whether an input is already safe, which is different from other techniques that ensure safe processing of input. Carefully perform root-cause analysis to be sure that the issue is not due to techniques that attempt to transform potentially-dangerous input into something safe, such as filtering (CWE-790) - which attempts to remove dangerous inputs - or encoding/escaping (CWE-116), which attempts to ensure that the input is not misinterpreted when it is included in output to another component. If the issue is truly due to imroper input validation, consider using lower-level children such as Improper Use of Validation Framework (CWE-1173) or improper validation involving specific types or properties of input such as Specified Quantity (CWE-1284); Specified Index, Position, or Offset (CWE-1285); Syntactic Correctness (CWE-1286); Specified Type (CWE-1287); Consistency within Input (CWE-1288); or Unsafe Equivalence (CWE-1289). | [
"Frequent Misuse",
"Frequent Misinterpretation",
"Abstraction"
] | [
{
"Comment": "Specified Quantity",
"CweID": "1284"
},
{
"Comment": "Specified Index, Position, or Offset",
"CweID": "1285"
},
{
"Comment": "Syntactic Correctness",
"CweID": "1286"
},
{
"Comment": "Specified Type",
"CweID": "1287"
},
{
"Comment": "Consistency withi... | null | null | null | null | null | 1 | [
[
"20"
]
] | [
"1284",
"129"
] |
1284 | Improper Validation of Specified Quantity in Input | Base | Simple | Incomplete | null | The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties. |
Specified quantities include size, length, frequency, price, rate, number of operations, time, and others. Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc. When the quantity is not properly validated, then attackers can specify malicious quantities to cause excessive resource allocation, trigger unexpected failures, enable buffer overflows, etc.
| null | [
{
"CweID": "20",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [
{
"Class": "Not Language-Specific",
"Name": null,
"Prevalence": "Often",
"Type": "Language"
}
] | [
{
"Note": null,
"Phase": "Implementation"
}
] | [
{
"Impact": [
"Varies by Context"
],
"Likelihood": null,
"Note": "Since quantities are used so often to affect resource allocation or process financial data, they are often present in many places in the code.",
"Scope": [
"Other"
]
}
] | null | [
{
"Description": "\n\nAssume all input is malicious. Use an \"accept known good\" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.\n\n\nWhen perfo... | [
{
"Entries": [
{
"BodyText": null,
"ExampleCode": null,
"IntroText": "This example demonstrates a shopping interaction in which the user is free to specify the quantity of items to be purchased and a total is calculated.",
"Language": null,
"Nature": null,
"... | [
{
"Description": "Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190).",
"Link": "https://www.cve.org/CVERecord?id=CVE-2022-21668",
"Reference": ... | null | null | null | [
{
"Note": "This entry is still under development and will continue to see updates and content improvements.",
"Type": "Maintenance"
}
] | [
{
"ContributionComment": null,
"ContributionDate": null,
"ContributionName": null,
"ContributionOrganization": null,
"ContributionReleaseDate": null,
"ContributionType": null,
"ContributionVersion": null,
"Date": null,
"ModificationComment": null,
"ModificationDate": null,
... | Allowed | This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities. | Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction. | [
"Acceptable-Use"
] | null | null | null | null | null | null | 1 | [
[
"20",
"1284"
]
] | [] |
129 | Improper Validation of Array Index | Variant | Simple | Draft | null | The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. | null | High | [
{
"CweID": "20",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [
{
"Class": null,
"Name": "C",
"Prevalence": "Often",
"Type": "Language"
},
{
"Class": null,
"Name": "C++",
"Prevalence": "Often",
"Type": "Language"
},
{
"Class": "Not Language-Specific",
"Name": null,
"Prevalence": "Undetermined",
"Type": "Language"
}
] | [
{
"Note": null,
"Phase": "Implementation"
}
] | [
{
"Impact": [
"DoS: Crash, Exit, or Restart"
],
"Likelihood": null,
"Note": "Use of an index that is outside the bounds of an array will very likely result in the corruption of relevant memory and perhaps instructions, leading to a crash, if the values are outside of the valid memory area.",
... | [
{
"Description": "\n\nThis weakness can often be detected using automated static analysis tools. Many modern tools use data flow analysis or constraint-based techniques to minimize the number of false positives.\n\n\nAutomated static analysis generally does not account for environmental considerations when repo... | [
{
"Description": "Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).",
"Effectiveness": null,
... | [
{
"Entries": [
{
"BodyText": null,
"ExampleCode": null,
"IntroText": "In the code snippet below, an untrusted integer value is used to reference an object in an array.",
"Language": null,
"Nature": null,
"Reference": null
},
{
"BodyText":... | [
{
"Description": "large ID in packet used as array index",
"Link": "https://www.cve.org/CVERecord?id=CVE-2005-0369",
"Reference": "CVE-2005-0369"
},
{
"Description": "negative array index as argument to POP LIST command",
"Link": "https://www.cve.org/CVERecord?id=CVE-2001-1009",
"Referen... | [
{
"EntryID": null,
"EntryName": "Unchecked array indexing",
"MappingFit": null,
"TaxonomyName": "CLASP"
},
{
"EntryID": null,
"EntryName": "INDEX - Array index overflow",
"MappingFit": null,
"TaxonomyName": "PLOVER"
},
{
"EntryID": "ARR00-C",
"EntryName": "Understand ... | [
"100"
] | [
{
"Authors": [
"Michael Howard",
"David LeBlanc"
],
"Edition": "2nd Edition",
"ExternalReferenceID": "REF-7",
"Publication": null,
"PublicationDay": "04",
"PublicationMonth": "12",
"PublicationYear": "2002",
"Publisher": "Microsoft Press",
"Section": "Chapter 5, \... | [
{
"Note": "This weakness can precede uncontrolled memory allocation (CWE-789) in languages that automatically expand an array when an index is used that is larger than the size of the array, such as JavaScript.",
"Type": "Relationship"
},
{
"Note": "An improperly validated array index might lead dir... | [
{
"ContributionComment": null,
"ContributionDate": null,
"ContributionName": null,
"ContributionOrganization": null,
"ContributionReleaseDate": null,
"ContributionType": null,
"ContributionVersion": null,
"Date": null,
"ModificationComment": null,
"ModificationDate": null,
... | Allowed | This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities. | Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction. | [
"Acceptable-Use"
] | null | [
{
"Description": "The most common condition situation leading to an out-of-bounds array index is the use of loop index variables as buffer indexes. If the end condition for the loop is subject to a flaw, the index can grow or shrink unbounded, therefore causing a buffer overflow or underflow. Another common sit... | [
{
"Description": null,
"Term": "out-of-bounds array index"
},
{
"Description": null,
"Term": "index-out-of-range"
},
{
"Description": null,
"Term": "array index underflow"
}
] | [
"Memory"
] | null | null | 1 | [
[
"20",
"129"
]
] | [] |
74 | Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') | Class | Simple | Incomplete | null | "The product constructs all or part of a command, data structure, or record using externally-influen(...TRUNCATED) | "Software or other automated logic has certain assumptions about what constitutes data and control r(...TRUNCATED) | High | [] | [
{
"Class": "Not Language-Specific",
"Name": null,
"Prevalence": "Undetermined",
"Type": "Language"
}
] | [{"Note":"REALIZATION: This weakness is caused during implementation of an architectural security ta(...TRUNCATED) | [{"Impact":["Read Application Data"],"Likelihood":null,"Note":"Many injection attacks involve the di(...TRUNCATED) | [{"Description":"Automated static analysis, commonly referred to as Static Application Security Test(...TRUNCATED) | [{"Description":"Programming languages and supporting technologies might be chosen which are not sub(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"This example code intends to take the (...TRUNCATED) | [{"Description":"API service using a large generative AI model allows direct prompt injection to lea(...TRUNCATED) | [{"EntryID":null,"EntryName":"Injection problem ('data' used as something else)","MappingFit":null,"(...TRUNCATED) | ["10","101","105","108","120","13","135","14","24","250","267","273","28","3","34","42","43","45","4(...TRUNCATED) | [{"Authors":["Secure Software, Inc."],"Edition":null,"ExternalReferenceID":"REF-18","Publication":nu(...TRUNCATED) | [{"Note":"Many people treat injection only as an input validation problem (CWE-20) because many peop(...TRUNCATED) | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Discouraged | CWE-74 is high-level and often misused when lower-level weaknesses are more appropriate. | Examine the children and descendants of this entry to find a more precise mapping. | [
"Frequent Misuse",
"Abstraction"
] | null | [
{
"Description": null,
"Ordinality": "Primary"
}
] | null | null | null | null | 1 | [
[
"74"
]
] | [
"1236",
"77",
"78",
"79",
"88",
"89",
"91",
"917",
"94"
] |
1236 | Improper Neutralization of Formula Elements in a CSV File | Base | Simple | Incomplete | null | "The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does no(...TRUNCATED) | "User-provided data is often saved to traditional databases. This data can be exported to a CSV file(...TRUNCATED) | null | [
{
"CweID": "74",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [{"Class":"Not Language-Specific","Name":null,"Prevalence":"Undetermined","Type":"Language"},{"Class(...TRUNCATED) | [{"Note":"The weakness is in the implementation of a software's CSV export feature, in particular ho(...TRUNCATED) | [{"Impact":["Read Application Data","Execute Unauthorized Code or Commands"],"Likelihood":["Low"],"N(...TRUNCATED) | null | [{"Description":"When generating CSV output, ensure that formula-sensitive metacharacters are effect(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"Hyperlinks or other commands can be ex(...TRUNCATED) | [{"Description":"Low privileged user can trigger CSV injection through a contact form field value","(...TRUNCATED) | null | null | [{"Authors":["OWASP"],"Edition":null,"ExternalReferenceID":"REF-21","Publication":null,"PublicationD(...TRUNCATED) | null | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Allowed | "This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for m(...TRUNCATED) | "Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do (...TRUNCATED) | [
"Acceptable-Use"
] | null | null | [{"Description":null,"Term":"CSV Injection"},{"Description":null,"Term":"Formula Injection"},{"Descr(...TRUNCATED) | null | null | null | 1 | [
[
"74",
"1236"
]
] | [] |
77 | Improper Neutralization of Special Elements used in a Command ('Command Injection') | Class | Simple | Draft | /data/images/CWE-77-Diagram.png | "The product constructs all or part of a command using externally-influenced input from an upstream (...TRUNCATED) | "\n\nMany protocols and products have their own custom command language. While OS or shell command s(...TRUNCATED) | High | [
{
"CweID": "74",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [{"Class":"Not Language-Specific","Name":null,"Prevalence":"Undetermined","Type":"Language"},{"Class(...TRUNCATED) | [{"Note":"\n\nCommand injection vulnerabilities typically occur when:\n\n\n 1. Data enters the appl(...TRUNCATED) | [{"Impact":["Execute Unauthorized Code or Commands"],"Likelihood":null,"Note":"If a malicious user i(...TRUNCATED) | [{"Description":"Automated static analysis, commonly referred to as Static Application Security Test(...TRUNCATED) | [{"Description":"If at all possible, use library calls rather than external processes to recreate th(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"Consider a \"CWE Differentiator\" appl(...TRUNCATED) | [{"Description":"injection of sed script syntax (\"sed injection\")","Link":"https://www.cve.org/CVE(...TRUNCATED) | [{"EntryID":null,"EntryName":"Command Injection","MappingFit":null,"TaxonomyName":"7 Pernicious King(...TRUNCATED) | [
"136",
"15",
"183",
"248",
"40",
"43",
"75",
"76"
] | [{"Authors":["Katrina Tsipenyuk","Brian Chess","Gary McGraw"],"Edition":null,"ExternalReferenceID":"(...TRUNCATED) | [{"Note":"\n\nThe \"command injection\" phrase carries different meanings, either as an attack or as(...TRUNCATED) | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Allowed-with-Review | CWE-77 is often misused when OS command injection (CWE-78) was intended instead [REF-1287]. | "Ensure that the analysis focuses on the root-cause error that allows the execution of commands, as (...TRUNCATED) | [
"Frequent Misuse"
] | [
{
"Comment": "OS Command Injection",
"CweID": "78"
}
] | [
{
"Description": null,
"Ordinality": "Primary"
}
] | [{"Description":"an attack-oriented phrase for this weakness. Note: often used when \"OS command inj(...TRUNCATED) | null | null | null | 1 | [
[
"74",
"77"
]
] | [] |
78 | Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') | Base | Simple | Stable | /data/images/CWE-78-Diagram.png | "The product constructs all or part of an OS command using externally-influenced input from an upstr(...TRUNCATED) | "\n\nThis weakness can lead to a vulnerability in environments in which the attacker does not have d(...TRUNCATED) | High | [
{
"CweID": "74",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [
{
"Class": "Not Language-Specific",
"Name": null,
"Prevalence": "Undetermined",
"Type": "Language"
}
] | [{"Note":"REALIZATION: This weakness is caused during implementation of an architectural security ta(...TRUNCATED) | [{"Impact":["Execute Unauthorized Code or Commands","DoS: Crash, Exit, or Restart","Read Files or Di(...TRUNCATED) | [{"Description":"\n\nThis weakness can often be detected using automated static analysis tools. Many(...TRUNCATED) | [{"Description":"If at all possible, use library calls rather than external processes to recreate th(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"This example code intends to take the (...TRUNCATED) | [{"Description":"OS command injection in Wi-Fi router, as exploited in the wild per CISA KEV.","Link(...TRUNCATED) | [{"EntryID":null,"EntryName":"OS Command Injection","MappingFit":null,"TaxonomyName":"PLOVER"},{"Ent(...TRUNCATED) | [
"108",
"15",
"43",
"6",
"88"
] | [{"Authors":["Greg Hoglund","Gary McGraw"],"Edition":null,"ExternalReferenceID":"REF-140","Publicati(...TRUNCATED) | [{"Note":"The \"OS command injection\" phrase carries different meanings to different people. For so(...TRUNCATED) | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Allowed | "This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for m(...TRUNCATED) | "Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do (...TRUNCATED) | [
"Acceptable-Use"
] | null | null | [{"Description":null,"Term":"Shell injection"},{"Description":null,"Term":"Shell metacharacters"},{"(...TRUNCATED) | [
"System Process"
] | [
"Program Invocation"
] | null | 1 | [
[
"74",
"78"
]
] | [] |
79 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | Base | Simple | Stable | /data/images/CWE-79-Diagram.png | "The product does not neutralize or incorrectly neutralizes user-controllable input before it is pla(...TRUNCATED) | "\n\nThere are many variants of cross-site scripting, characterized by a variety of terms or involvi(...TRUNCATED) | High | [
{
"CweID": "74",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [{"Class":"Not Language-Specific","Name":null,"Prevalence":"Undetermined","Type":"Language"},{"Class(...TRUNCATED) | [{"Note":"REALIZATION: This weakness is caused during implementation of an architectural security ta(...TRUNCATED) | [{"Impact":["Bypass Protection Mechanism","Read Application Data"],"Likelihood":null,"Note":"The mos(...TRUNCATED) | [{"Description":"Use automated static analysis tools that target this type of weakness. Many modern (...TRUNCATED) | [{"Description":"\n\nUse a vetted library or framework that does not allow this weakness to occur or(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"The following code displays a welcome (...TRUNCATED) | [{"Description":"Python Library Manager did not sufficiently neutralize a user-supplied search term,(...TRUNCATED) | [{"EntryID":null,"EntryName":"Cross-site scripting (XSS)","MappingFit":null,"TaxonomyName":"PLOVER"}(...TRUNCATED) | [
"209",
"588",
"591",
"592",
"63",
"85"
] | [{"Authors":["Jeremiah Grossman","Robert \"RSnake\" Hansen","Petko \"pdp\" D. Petkov","Anton Rager",(...TRUNCATED) | [{"Note":"\n\nThe attack methods for XSS can vary depending on the type of XSS and the attacker’s (...TRUNCATED) | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Allowed | "This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for m(...TRUNCATED) | "Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do (...TRUNCATED) | [
"Acceptable-Use"
] | null | [
{
"Description": null,
"Ordinality": "Resultant"
}
] | [{"Description":"A common abbreviation for Cross-Site Scripting.","Term":"XSS"},{"Description":"Used(...TRUNCATED) | null | null | ["\n\nThe Same Origin Policy states that browsers should limit the resources accessible to scripts r(...TRUNCATED) | 1 | [
[
"74",
"79"
]
] | [] |
88 | Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') | Base | Simple | Draft | null | "The product constructs a string for a command to be executed by a separate component\nin another co(...TRUNCATED) | "\n\nWhen creating commands using interpolation into a string, developers may assume that only the a(...TRUNCATED) | null | [
{
"CweID": "74",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [{"Class":"Not Language-Specific","Name":null,"Prevalence":"Undetermined","Type":"Language"},{"Class(...TRUNCATED) | [{"Note":"REALIZATION: This weakness is caused during implementation of an architectural security ta(...TRUNCATED) | [{"Impact":["Execute Unauthorized Code or Commands","Alter Execution Logic","Read Application Data",(...TRUNCATED) | [{"Description":"Automated static analysis, commonly referred to as Static Application Security Test(...TRUNCATED) | [{"Description":"Where possible, avoid building a single string that contains the command and its ar(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"Consider the following program. It int(...TRUNCATED) | [{"Description":"Python-based dependency management tool avoids OS command injection when generating(...TRUNCATED) | [{"EntryID":null,"EntryName":"Argument Injection or Modification","MappingFit":null,"TaxonomyName":"(...TRUNCATED) | [
"137",
"174",
"41",
"460",
"88"
] | [{"Authors":["Steven Christey"],"Edition":null,"ExternalReferenceID":"REF-859","Publication":null,"P(...TRUNCATED) | [{"Note":"At one layer of abstraction, this can overlap other weaknesses that have whitespace proble(...TRUNCATED) | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Allowed | "This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for m(...TRUNCATED) | "Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do (...TRUNCATED) | [
"Acceptable-Use"
] | null | [
{
"Description": null,
"Ordinality": "Primary"
}
] | null | [
"System Process"
] | null | null | 1 | [
[
"74",
"88"
]
] | [] |
89 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') | Base | Simple | Stable | /data/images/CWE-89-Diagram.png | "The product constructs all or part of an SQL command using externally-influenced input from an upst(...TRUNCATED) | null | High | [
{
"CweID": "74",
"Nature": "ChildOf",
"Ordinal": "Primary",
"ViewID": "1003"
}
] | [{"Class":"Not Language-Specific","Name":null,"Prevalence":"Undetermined","Type":"Language"},{"Class(...TRUNCATED) | [{"Note":"REALIZATION: This weakness is caused during implementation of an architectural security ta(...TRUNCATED) | [{"Impact":["Execute Unauthorized Code or Commands"],"Likelihood":null,"Note":"Adversaries could exe(...TRUNCATED) | [{"Description":"\n\nThis weakness can often be detected using automated static analysis tools. Many(...TRUNCATED) | [{"Description":"\n\nUse a vetted library or framework that does not allow this weakness to occur or(...TRUNCATED) | [{"Entries":[{"BodyText":null,"ExampleCode":null,"IntroText":"In 2008, a large number of web servers(...TRUNCATED) | [{"Description":"SQL injection in security product dashboard using crafted certificate fields","Link(...TRUNCATED) | [{"EntryID":null,"EntryName":"SQL injection","MappingFit":null,"TaxonomyName":"PLOVER"},{"EntryID":n(...TRUNCATED) | [
"108",
"109",
"110",
"470",
"66",
"7"
] | [{"Authors":["rain.forest.puppy"],"Edition":null,"ExternalReferenceID":"REF-1460","Publication":"Phr(...TRUNCATED) | [{"Note":"SQL injection can be resultant from special character mismanagement, MAID, or denylist/all(...TRUNCATED) | [{"ContributionComment":null,"ContributionDate":null,"ContributionName":null,"ContributionOrganizati(...TRUNCATED) | Allowed | "This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for m(...TRUNCATED) | "Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do (...TRUNCATED) | [
"Acceptable-Use"
] | null | null | [{"Description":"a common attack-oriented phrase","Term":"SQL injection"},{"Description":"a common a(...TRUNCATED) | null | null | null | 1 | [
[
"74",
"89"
]
] | [] |
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 11