Datasets:

witrin
/

vice

Error code:   DatasetGenerationCastError
Exception:    DatasetGenerationCastError
Message:      An error occurred while generating the dataset

All the data files must have the same columns, but at some point there are 1 new columns ({'repository'}) and 12 missing columns ({'status', 'mapping', 'parents', 'summary', 'name', 'abstraction', 'detection', 'alternates', 'introduction', 'notes', 'consequences', 'platform'}).

This happened while the json dataset builder was generating data using

hf://datasets/witrin/vice/auxiliary/respository.jsonl (at revision 125c041975a5b226f6c25d4f41f3415c3bf87a70)

Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback:    Traceback (most recent call last):
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1870, in _prepare_split_single
                  writer.write_table(table)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/arrow_writer.py", line 622, in write_table
                  pa_table = table_cast(pa_table, self._schema)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2292, in table_cast
                  return cast_table_to_schema(table, schema)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/table.py", line 2240, in cast_table_to_schema
                  raise CastError(
              datasets.table.CastError: Couldn't cast
              identifier: string
              repository: struct<allow_forking: bool, archive_url: string, archived: bool, assignees_url: string, blobs_url: string, branches_url: string, clone_url: string, collaborators_url: string, comments_url: string, commits_url: string, compare_url: string, contents_url: string, contributors_url: string, created_at: timestamp[s], custom_properties: struct<enforce_policies: string, policy_commit_signing: string, policy_mainline_branch: string, last_reviewed: timestamp[s], team: list<item: string>, vanta_production_branch_name: string, dependency-review-action-enabled: string, durableOwnershipDisable: string, durableOwnershipNextCheckDate: string, durableOwnershipWarn: string, SecurityCategory: string, exemptFromGlobalRepoRules: string, department: string, mirror-status: string, is-deprecated: string, is-published-component: string, maintenance-mode: string, eclipse_project: string, Documentation: string, DisCatSharp: string, Scope: string>, default_branch: string, deployments_url: string, description: string, disabled: bool, downloads_url: string, events_url: string, fork: bool, forks: int64, forks_count: int64, forks_url: string, full_name: string, git_commits_url: string, git_refs_url: string, git_tags_url: string, git_url: string, has_discussions: bool, has_downloads: bool, has_issues: bool, has_pages: bool, has_projects: bool, has_wiki: bool, homepage: string, hooks_url: string, html_url: string, id: int64, is_template: bool, issue_comment_url: string, issue_ev
              ...
              ogin: string
                        child 9, node_id: string
                        child 10, organizations_url: string
                        child 11, received_events_url: string
                        child 12, repos_url: string
                        child 13, site_admin: bool
                        child 14, starred_url: string
                        child 15, subscriptions_url: string
                        child 16, type: string
                        child 17, url: string
                        child 18, user_view_type: string
                    child 57, permissions: struct<admin: bool, maintain: bool, pull: bool, push: bool, triage: bool>
                        child 0, admin: bool
                        child 1, maintain: bool
                        child 2, pull: bool
                        child 3, push: bool
                        child 4, triage: bool
                    child 58, private: bool
                    child 59, pulls_url: string
                    child 60, pushed_at: timestamp[s]
                    child 61, releases_url: string
                    child 62, size: int64
                    child 63, ssh_url: string
                    child 64, stargazers_count: int64
                    child 65, stargazers_url: string
                    child 66, statuses_url: string
                    child 67, subscribers_url: string
                    child 68, subscription_url: string
                    child 69, svn_url: string
                    child 70, tags_url: string
                    child 71, teams_url: string
                    child 72, topics: list<item: string>
                        child 0, item: string
                    child 73, trees_url: string
                    child 74, updated_at: timestamp[s]
                    child 75, url: string
                    child 76, visibility: string
                    child 77, watchers: int64
                    child 78, watchers_count: int64
                    child 79, web_commit_signoff_required: bool
              to
              {'identifier': Value(dtype='string', id=None), 'name': Value(dtype='string', id=None), 'alternates': [{'term': Value(dtype='string', id=None), 'description': Value(dtype='string', id=None)}], 'status': Value(dtype='string', id=None), 'abstraction': Value(dtype='string', id=None), 'summary': Value(dtype='string', id=None), 'detection': [{'method': Value(dtype='string', id=None), 'description': Value(dtype='string', id=None)}], 'platform': {'technology': Value(dtype='string', id=None), 'language': Value(dtype='string', id=None)}, 'introduction': [{'phase': Value(dtype='string', id=None)}], 'notes': [{'note': Value(dtype='string', id=None), 'type': Value(dtype='string', id=None)}], 'mapping': {'usage': Value(dtype='string', id=None)}, 'consequences': [{'scope': Value(dtype='string', id=None), 'note': Value(dtype='string', id=None)}], 'parents': Sequence(feature=Value(dtype='string', id=None), length=-1, id=None)}
              because column names don't match
              
              During handling of the above exception, another exception occurred:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1420, in compute_config_parquet_and_info_response
                  parquet_operations = convert_to_parquet(builder)
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1052, in convert_to_parquet
                  builder.download_and_prepare(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 924, in download_and_prepare
                  self._download_and_prepare(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1000, in _download_and_prepare
                  self._prepare_split(split_generator, **prepare_split_kwargs)
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1741, in _prepare_split
                  for job_id, done, content in self._prepare_split_single(
                File "/src/services/worker/.venv/lib/python3.9/site-packages/datasets/builder.py", line 1872, in _prepare_split_single
                  raise DatasetGenerationCastError.from_cast_error(
              datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
              
              All the data files must have the same columns, but at some point there are 1 new columns ({'repository'}) and 12 missing columns ({'status', 'mapping', 'parents', 'summary', 'name', 'abstraction', 'detection', 'alternates', 'introduction', 'notes', 'consequences', 'platform'}).
              
              This happened while the json dataset builder was generating data using
              
              hf://datasets/witrin/vice/auxiliary/respository.jsonl (at revision 125c041975a5b226f6c25d4f41f3415c3bf87a70)
              
              Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

identifier string	name string	alternates list	status string	abstraction string	summary string	detection list	platform dict	introduction list	notes sequence	mapping dict	consequences list	parents sequence
1004	Sensitive Cookie Without 'HttpOnly' Flag	[]	Incomplete	Variant	The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": "Web Based", "language": "Not Language-Specific" }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Confidentiality", "note": "If the HttpOnly flag is not set, then sensitive information stored in the cookie may be exposed to unintended parties." }, { "scope": "Integrity", "note": "If the cookie in question is an authentication cookie, then not setting the HttpOnly flag may allow an adversary to steal authentication data (e.g., a session ID) and assume the identity of the user." } ]	[ "732" ]
1007	Insufficient Visual Distinction of Homoglyphs Presented to User	[ { "term": "Homograph Attack", "description": "\"Homograph\" is often used as a synonym of \"homoglyph\" by researchers, but according to Wikipedia, a homograph is a word that has multiple, distinct meanings." } ]	Incomplete	Base	The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.	[ { "method": "Manual Dynamic Analysis", "description": "If utilizing user accounts, attempt to submit a username that contains homoglyphs. Similarly, check to see if links containing homoglyphs can be sent via email, web browsers, or other mechanisms." } ]	{ "technology": "Web Based", "language": "Not Language-Specific" }	[ { "phase": "Architecture and Design" }, { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Integrity", "note": "An attacker may ultimately redirect a user to a malicious website, by deceiving the user into believing the URL they are accessing is a trusted domain. However, the attack can also be used to forge log entries by using homoglyphs in usernames. Homoglyph manipulations are often the first step towards executing advanced attacks such as stealing a user's credentials, Cross-Site Scripting (XSS), or log forgery. If an attacker redirects a user to a malicious site, the attacker can mimic a trusted domain to steal account credentials and perform actions on behalf of the user, without the user's knowledge. Similarly, an attacker could create a username for a website that contains homoglyph characters, making it difficult for an admin to review logs and determine which users performed which actions." } ]	[ "451" ]
102	Struts: Duplicate Validation Forms	[]	Incomplete	Variant	The product uses multiple validation forms with the same name, which might cause the Struts Validator to validate a form that the programmer does not expect.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Integrity", "note": "" } ]	[ "694", "1173", "20" ]
1021	Improper Restriction of Rendered UI Layers or Frames	[ { "term": "Clickjacking", "description": "" }, { "term": "UI Redress Attack", "description": "" }, { "term": "Tapjacking", "description": "\"Tapjacking\" is similar to clickjacking, except it is used for mobile applications in which the user \"taps\" the application instead of performing a mouse click." } ]	Incomplete	Base	The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": "Web Based", "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Access Control", "note": "An attacker can trick a user into performing actions that are masked and hidden from the user's view. The impact varies widely, depending on the functionality of the underlying application. For example, in a social media application, clickjacking could be used to trik the user into changing privacy settings." } ]	[ "441", "610", "451" ]
1022	Use of Web Link to Untrusted Target with window.opener Access	[ { "term": "tabnabbing", "description": "" } ]	Incomplete	Variant	The web application produces links to untrusted external sites outside of its sphere of control, but it does not properly prevent the external site from modifying security-critical properties of the window.opener object, such as the location property.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": "Web Based", "language": null }	[ { "phase": "Architecture and Design" }, { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Confidentiality", "note": "The user may be redirected to an untrusted page that contains undesired content or malicious script code." } ]	[ "266" ]
1023	Incomplete Comparison with Missing Factors	[]	Incomplete	Class	The product performs a comparison between entities that must consider multiple factors or characteristics of each entity, but the comparison does not include one or more of these factors.	[]	{ "technology": null, "language": "Not Language-Specific" }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed-with-Review" }	[ { "scope": "Integrity", "note": "" } ]	[ "697" ]
1024	Comparison of Incompatible Types	[]	Incomplete	Base	The product performs a comparison between two entities, but the entities are of different, incompatible types that cannot be guaranteed to provide correct results when they are directly compared.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "697" ]
1025	Comparison Using Wrong Factors	[]	Incomplete	Base	The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.	[]	{ "technology": null, "language": "Not Language-Specific" }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "697" ]
103	Struts: Incomplete validate() Method Definition	[]	Draft	Variant	The product has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate().	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[ { "note": "This could introduce other weaknesses related to missing input validation.", "type": "Relationship" }, { "note": "The current description implies a loose composite of two separate weaknesses, so this node might need to be split or converted into a low-level category.", "type": "Maintenance" } ]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "Disabling the validation framework for a form exposes the product to numerous types of attacks. Unchecked input is the root cause of vulnerabilities like cross-site scripting, process control, and SQL injection." }, { "scope": "Confidentiality", "note": "Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack." } ]	[ "573", "20" ]
1037	Processor Optimization Removal or Modification of Security-critical Code	[]	Incomplete	Base	The developer builds a security-critical protection mechanism into the software, but the processor optimizes the execution of the program such that the mechanism is removed or modified.	[ { "method": "White Box", "description": "In theory this weakness can be detected through the use of white box testing techniques where specifically crafted test cases are used in conjunction with debuggers to verify the order of statements being executed." } ]	{ "technology": null, "language": "Not Language-Specific" }	[ { "phase": "Architecture and Design" } ]	[ { "note": "As of CWE 4.9, members of the CWE Hardware SIG are closely analyzing this entry and others to improve CWE's coverage of transient execution weaknesses, which include issues related to Spectre, Meltdown, and other attacks. Additional investigation may include other weaknesses related to microarchitectural state. As a result, this entry might change significantly in CWE 4.10.", "type": "Maintenance" } ]	{ "usage": "Allowed" }	[ { "scope": "Integrity", "note": "A successful exploitation of this weakness will change the order of an application's execution and will likely be used to bypass specific protection mechanisms. This bypass can be exploited further to potentially read data that should otherwise be unaccessible." } ]	[ "1038" ]
1038	Insecure Automated Optimizations	[]	Draft	Class	The product uses a mechanism that automatically optimizes code, e.g. to improve a characteristic such as performance, but the optimizations can have an unintended side effect that might violate an intended security assumption.	[]	{ "technology": null, "language": "Not Language-Specific" }	[ { "phase": "Architecture and Design" } ]	[]	{ "usage": "Allowed-with-Review" }	[ { "scope": "Integrity", "note": "The optimizations alter the order of execution resulting in side effects that were not intended by the original developer." } ]	[ "435", "758" ]
1039	Automated Recognition Mechanism with Inadequate Detection or Handling of Adversarial Input Perturbations	[]	Incomplete	Class	The product uses an automated mechanism such as machine learning to recognize complex data inputs (e.g. image or audio) as a particular concept or category, but it does not properly detect or handle inputs that have been modified or constructed in a way that causes the mechanism to detect a different, incorrect concept.	[]	{ "technology": null, "language": "Not Language-Specific" }	[ { "phase": "Architecture and Design" } ]	[ { "note": "Further investigation is needed to determine if better relationships exist or if additional organizational entries need to be created. For example, this issue might be better related to \"recognition of input as an incorrect type,\" which might place it as a sibling of CWE-704 (incorrect type conversion).", "type": "Relationship" } ]	{ "usage": "Allowed-with-Review" }	[ { "scope": "Integrity", "note": "When the automated recognition is used in a protection mechanism, an attacker may be able to craft inputs that are misinterpreted in a way that grants excess privileges." } ]	[ "693", "697" ]
104	Struts: Form Bean Does Not Extend Validation Class	[]	Draft	Variant	If a form bean does not extend an ActionForm subclass of the Validator framework, it can expose the application to other weaknesses related to insufficient input validation.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "Bypassing the validation framework for a form exposes the application to numerous types of attacks. Unchecked input is an important component of vulnerabilities like cross-site scripting, process control, and SQL injection." }, { "scope": "Confidentiality", "note": "Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack." } ]	[ "573", "20" ]
1041	Use of Redundant Code	[]	Incomplete	Base	The product has multiple functions, methods, procedures, macros, etc. that contain the same code.	[]	{ "technology": null, "language": "Not Language-Specific" }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1042	Static Member Data Element outside of a Singleton Class Element	[]	Incomplete	Variant	The code contains a member element that is declared as static (but not final), in which its parent class element is not a singleton class - that is, a class element that can be used only once in the 'to' association of a Create action.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1176" ]
1043	Data Element Aggregating an Excessively Large Number of Non-Primitive Elements	[]	Incomplete	Base	The product uses a data element that has an excessively large number of sub-elements with non-primitive data types such as structures or aggregated objects.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1093" ]
1044	Architecture with Number of Horizontal Layers Outside of Expected Range	[]	Incomplete	Base	The product's architecture contains too many - or too few - horizontal layers.	[]	{ "technology": null, "language": null }	[ { "phase": "Architecture and Design" } ]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1045	Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor	[]	Incomplete	Base	A parent class has a virtual destructor method, but the parent has a child class that does not have a virtual destructor.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
1046	Creation of Immutable Text Using String Concatenation	[]	Incomplete	Base	The product creates an immutable text string using string concatenation operations.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1176" ]
1047	Modules with Circular Dependencies	[]	Incomplete	Base	The product contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1048	Invokable Control Element with Large Number of Outward Calls	[]	Incomplete	Base	The code contains callable control elements that contain an excessively large number of references to other application objects external to the context of the callable, i.e. a Fan-Out value that is excessively large.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1049	Excessive Data Query Operations in a Large Data Table	[]	Incomplete	Base	The product performs a data query with a large number of joins and sub-queries on a large data table.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1176" ]
105	Struts: Form Field Without Validator	[]	Draft	Variant	The product has a form field that is not validated by a corresponding validation form, which can introduce other weaknesses related to insufficient input validation.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Integrity", "note": "" }, { "scope": "Integrity", "note": "If unused fields are not validated, shared business logic in an action may allow attackers to bypass the validation checks that are performed for other uses of the form." } ]	[ "1173", "20" ]
1050	Excessive Platform Resource Consumption within a Loop	[]	Incomplete	Base	The product has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "405" ]
1051	Initialization with Hard-Coded Network Resource Configuration Data	[]	Incomplete	Base	The product initializes data using hard-coded values that act as network resource identifiers.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1419" ]
1052	Excessive Use of Hard-Coded Literals in Initialization	[]	Incomplete	Base	The product initializes a data element using a hard-coded literal that is not a simple integer or static constant element.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1419" ]
1053	Missing Documentation for Design	[]	Incomplete	Base	The product does not have documentation that represents how it is designed.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1059" ]
1054	Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer	[]	Incomplete	Base	The code at one architectural layer invokes code that resides at a deeper layer than the adjacent layer, i.e., the invocation skips at least one layer, and the invoked code is not part of a vertical utility layer that can be referenced from any horizontal layer.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1061" ]
1055	Multiple Inheritance from Concrete Classes	[]	Incomplete	Base	The product contains a class with inheritance from more than one concrete class.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1093" ]
1056	Invokable Control Element with Variadic Parameters	[]	Incomplete	Base	A named-callable or method control element has a signature that supports a variable (variadic) number of parameters or arguments.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1057	Data Access Operations Outside of Expected Data Manager Component	[]	Incomplete	Base	The product uses a dedicated, central data manager component as required by design, but it contains code that performs data-access operations that do not use this data manager.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1061" ]
1058	Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element	[]	Incomplete	Base	The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member data element.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "662" ]
1059	Insufficient Technical Documentation	[]	Incomplete	Class	The product does not contain sufficient technical or engineering documentation (whether on paper or in electronic form) that contains descriptions of all the relevant software/hardware elements of the product, such as its usage, structure, architectural components, interfaces, design, implementation, configuration, operation, etc.	[]	{ "technology": "Not Technology-Specific", "language": "Not Language-Specific" }	[ { "phase": "Architecture and Design" }, { "phase": "Documentation" } ]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "Without a method of verification, one cannot be sure that everything only functions as expected." } ]	[ "710" ]
106	Struts: Plug-in Framework not in Use	[]	Draft	Variant	When an application does not use an input validation framework such as the Struts Validator, there is a greater risk of introducing weaknesses related to insufficient input validation.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Integrity", "note": "" } ]	[ "1173", "20" ]
1060	Excessive Number of Inefficient Server-Side Data Accesses	[]	Incomplete	Base	The product performs too many data queries without using efficient data processing functionality such as stored procedures.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1061	Insufficient Encapsulation	[]	Incomplete	Class	The product does not sufficiently hide the internal representation and implementation details of data or methods, which might allow external components or modules to modify data unexpectedly, invoke unexpected functionality, or introduce dependencies that the programmer did not intend.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed-with-Review" }	[]	[ "710" ]
1062	Parent Class with References to Child Class	[]	Incomplete	Base	The code has a parent class that contains references to a child class, its methods, or its members.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1061" ]
1063	Creation of Class Instance within a Static Code Block	[]	Incomplete	Base	A static code block creates an instance of a class.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1176" ]
1064	Invokable Control Element with Signature Containing an Excessive Number of Parameters	[]	Incomplete	Base	The product contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1065	Runtime Resource Management Control Element in a Component Built to Run on Application Servers	[]	Incomplete	Base	The product uses deployed components from application servers, but it also uses low-level functions/methods for management of resources, instead of the API provided by the application server.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1066	Missing Serialization Control Element	[]	Incomplete	Base	The product contains a serializable data element that does not have an associated serialization method.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1067	Excessive Execution of Sequential Searches of Data Resource	[]	Incomplete	Base	The product contains a data query against an SQL table or view that is configured in a way that does not utilize an index and may cause sequential searches to be performed.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1176" ]
1068	Inconsistency Between Implementation and Documented Design	[]	Incomplete	Base	The implementation of the product is not consistent with the design as described within the relevant documentation.	[]	{ "technology": "Not Technology-Specific", "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Prohibited" }	[]	[ "710" ]
1069	Empty Exception Block	[]	Incomplete	Variant	An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.	[]	{ "technology": null, "language": "Not Language-Specific" }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1071" ]
107	Struts: Unused Validation Form	[]	Draft	Variant	An unused validation form indicates that validation logic is not up-to-date.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" }, { "phase": "Operation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1164", "20" ]
1070	Serializable Data Element Containing non-Serializable Item Elements	[]	Incomplete	Base	The product contains a serializable, storable data element such as a field or member, but the data element contains member elements that are not serializable.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
1071	Empty Code Block	[]	Incomplete	Base	The source code contains a block that does not contain any code, i.e., the block is empty.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1164" ]
1072	Data Resource Access without Use of Connection Pooling	[]	Incomplete	Base	The product accesses a data resource through a database without using a connection pooling capability.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "405" ]
1073	Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses	[]	Incomplete	Base	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.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "405" ]
1074	Class with Excessively Deep Inheritance	[]	Incomplete	Base	A class has an inheritance level that is too high, i.e., it has a large number of parent classes.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1093" ]
1075	Unconditional Control Flow Transfer outside of Switch Block	[]	Incomplete	Base	The product performs unconditional control transfer (such as a "goto") in code outside of a branching structure such as a switch block.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1076	Insufficient Adherence to Expected Conventions	[]	Incomplete	Class	The product's architecture, source code, design, documentation, or other artifact does not follow required conventions.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1077	Floating Point Comparison with Incorrect Operator	[]	Incomplete	Variant	The code performs a comparison such as an equality test between two float (floating point) values, but it uses comparison operators that do not account for the possibility of loss of precision.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "697" ]
1078	Inappropriate Source Code Style or Formatting	[]	Incomplete	Class	The source code does not follow desired style or formatting for indentation, white space, comments, etc.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1076" ]
1079	Parent Class without Virtual Destructor Method	[]	Incomplete	Base	A parent class contains one or more child classes, but the parent class does not have a virtual destructor method.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
108	Struts: Unvalidated Action Form	[]	Incomplete	Variant	Every Action Form must have a corresponding validation form.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "If an action form mapping does not have a validation form defined, it may be vulnerable to a number of attacks that rely on unchecked input. Unchecked input is the root cause of some of today's worst and most common software security problems. Cross-site scripting, SQL injection, and process control vulnerabilities all stem from incomplete or absent input validation." }, { "scope": "Confidentiality", "note": "Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack." } ]	[ "1173", "20" ]
1080	Source Code File with Excessive Number of Lines of Code	[]	Incomplete	Base	A source code file has too many lines of code.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1082	Class Instance Self Destruction Control Element	[]	Incomplete	Base	The code contains a class instance that calls the method or function to delete or destroy itself.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
1083	Data Access from Outside Expected Data Manager Component	[]	Incomplete	Base	The product is intended to manage data access through a particular data manager component such as a relational or non-SQL database, but it contains code that performs data access operations without using that component.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1061" ]
1084	Invokable Control Element with Excessive File or Data Access Operations	[]	Incomplete	Base	A function or method contains too many operations that utilize a data manager or file resource.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "405" ]
1085	Invokable Control Element with Excessive Volume of Commented-out Code	[]	Incomplete	Base	A function, method, procedure, etc. contains an excessive amount of code that has been commented out within its body.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1078" ]
1086	Class with Excessive Number of Child Classes	[]	Incomplete	Base	A class contains an unnecessarily large number of children.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1093" ]
1087	Class with Virtual Method without a Virtual Destructor	[]	Incomplete	Base	A class contains a virtual method, but the method does not have an associated virtual destructor.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
1088	Synchronous Access of Remote Resource without Timeout	[]	Incomplete	Base	The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "821" ]
1089	Large Data Table with Excessive Number of Indices	[]	Incomplete	Base	The product uses a large data table that contains an excessively large number of indices.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "405" ]
109	Struts: Validator Turned Off	[]	Draft	Variant	Automatic filtering via a Struts bean has been turned off, which disables the Struts Validator and custom validation logic. This exposes the application to other weaknesses related to insufficient input validation.	[]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[ { "note": "The Action Form mapping in the demonstrative example disables the form's validate() method. The Struts bean: write tag automatically encodes special HTML characters, replacing a < with \"<\" and a > with \">\". This action can be disabled by specifying filter=\"false\" as an attribute of the tag to disable specified JSP pages. However, being disabled makes these pages susceptible to cross-site scripting attacks. An attacker may be able to insert malicious scripts as user input to write to these JSP pages.", "type": "Other" } ]	{ "usage": "Allowed" }	[ { "scope": "Access Control", "note": "" } ]	[ "1173", "20" ]
1090	Method Containing Access of a Member Element from Another Class	[]	Incomplete	Base	A method for a class performs an operation that directly accesses a member element from another class.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1061" ]
1091	Use of Object without Invoking Destructor Method	[]	Incomplete	Base	The product contains a method that accesses an object but does not later invoke the element's associated finalize/destructor method.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "772", "1076" ]
1092	Use of Same Invokable Control Element in Multiple Architectural Layers	[]	Incomplete	Base	The product uses the same control element across multiple architectural layers.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1093	Excessively Complex Data Representation	[]	Incomplete	Class	The product uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed-with-Review" }	[ { "scope": "Other", "note": "" }, { "scope": "Other", "note": "" } ]	[ "710" ]
1094	Excessive Index Range Scan for a Data Resource	[]	Incomplete	Base	The product contains an index range scan for a large data table, but the scan can cover a large number of rows.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "405" ]
1095	Loop Condition Value Update within the Loop	[]	Incomplete	Base	The product uses a loop with a control flow condition based on a value that is updated within the body of the loop.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
1096	Singleton Class Instance Creation without Proper Locking or Synchronization	[]	Incomplete	Variant	The product implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "820", "662" ]
1097	Persistent Storable Data Element without Associated Comparison Control Element	[]	Incomplete	Base	The product uses a storable data element that does not have all of the associated functions or methods that are necessary to support comparison.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1076", "595" ]
1098	Data Element containing Pointer Item without Proper Copy Control Element	[]	Incomplete	Base	The code contains a data element with a pointer that does not have an associated copy or constructor method.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
1099	Inconsistent Naming Conventions for Identifiers	[]	Incomplete	Base	The product's code, documentation, or other artifacts do not consistently use the same naming conventions for variables, callables, groups of related callables, I/O capabilities, data types, file names, or similar types of elements.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1078" ]
11	ASP.NET Misconfiguration: Creating Debug Binary	[]	Draft	Variant	Debugging messages help attackers learn about the system and plan a form of attack.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": null, "language": null }	[ { "phase": "Implementation" }, { "phase": "Build and Compilation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Confidentiality", "note": "Attackers can leverage the additional information they gain from debugging output to mount attacks targeted on the framework, database, or other resources used by the application." } ]	[ "489" ]
110	Struts: Validator Without Form Field	[]	Draft	Variant	Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.	[ { "method": "Automated Static Analysis", "description": "To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files." }, { "method": "Manual Static Analysis", "description": "To find the issue in the implementation, manual checks or automated static analysis could be applied to the XML configuration files." } ]	{ "technology": null, "language": null }	[ { "phase": "Implementation" }, { "phase": "Operation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "It is critically important that validation logic be maintained and kept in sync with the rest of the application. Unchecked input is the root cause of some of today's worst and most common software security problems. Cross-site scripting, SQL injection, and process control vulnerabilities all stem from incomplete or absent input validation." } ]	[ "1164", "20" ]
1100	Insufficient Isolation of System-Dependent Functions	[]	Incomplete	Base	The product or code does not isolate system-dependent functionality into separate standalone modules.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1061" ]
1101	Reliance on Runtime Component in Generated Code	[]	Incomplete	Base	The product uses automatically-generated code that cannot be executed without a specific runtime support component.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "710" ]
1102	Reliance on Machine-Dependent Data Representation	[]	Incomplete	Base	The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "758" ]
1103	Use of Platform-Dependent Third Party Components	[]	Incomplete	Base	The product relies on third-party components that do not provide equivalent functionality across all desirable platforms.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "758" ]
1104	Use of Unmaintained Third Party Components	[]	Incomplete	Base	The product relies on third-party components that are not actively supported or maintained by the original developer or a trusted proxy for the original developer.	[]	{ "technology": "Not Technology-Specific", "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1357" ]
1105	Insufficient Encapsulation of Machine-Dependent Functionality	[]	Incomplete	Base	The product or code uses machine-dependent functionality, but it does not sufficiently encapsulate or isolate this functionality from the rest of the code.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "758", "1061" ]
1106	Insufficient Use of Symbolic Constants	[]	Incomplete	Base	The source code uses literal constants that may need to change or evolve over time, instead of using symbolic constants.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1078" ]
1107	Insufficient Isolation of Symbolic Constant Definitions	[]	Incomplete	Base	The source code uses symbolic constants, but it does not sufficiently place the definitions of these constants into a more centralized or isolated location.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1078" ]
1108	Excessive Reliance on Global Variables	[]	Incomplete	Base	The code is structured in a way that relies too much on using or setting global variables throughout various points in the code, instead of preserving the associated information in a narrower, more local context.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1076" ]
1109	Use of Same Variable for Multiple Purposes	[]	Incomplete	Base	The code contains a callable, block, or other code element in which the same variable is used to control more than one unique task or store more than one instance of data.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1078" ]
111	Direct Use of Unsafe JNI	[]	Draft	Variant	When a Java application uses the Java Native Interface (JNI) to call code written in another programming language, it can expose the application to weaknesses in that code, even if those weaknesses cannot occur in Java.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": null, "language": null }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Access Control", "note": "" } ]	[ "695", "20" ]
1110	Incomplete Design Documentation	[]	Incomplete	Base	The product's design documentation does not adequately describe control flow, data flow, system initialization, relationships between tasks, components, rationales, or other important aspects of the design.	[]	{ "technology": "Not Technology-Specific", "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1059" ]
1111	Incomplete I/O Documentation	[]	Incomplete	Base	The product's documentation does not adequately define inputs, outputs, or system/software interfaces.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1059" ]
1112	Incomplete Documentation of Program Execution	[]	Incomplete	Base	The document does not fully define all mechanisms that are used to control or influence how product-specific programs are executed.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1059" ]
1113	Inappropriate Comment Style	[]	Incomplete	Base	The source code uses comment styles or formats that are inconsistent or do not follow expected standards for the product.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1078" ]
1114	Inappropriate Whitespace Style	[]	Incomplete	Base	The source code contains whitespace that is inconsistent across the code or does not follow expected standards for the product.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1078" ]
1115	Source Code Element without Standard Prologue	[]	Incomplete	Base	The source code contains elements such as source files that do not consistently provide a prologue or header that has been standardized for the project.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1078" ]
1116	Inaccurate Comments	[]	Incomplete	Base	The source code contains comments that do not accurately describe or explain aspects of the portion of the code with which the comment is associated.	[]	{ "technology": null, "language": "Not Language-Specific" }	[]	[]	{ "usage": "Allowed" }	[ { "scope": "Other", "note": "" } ]	[ "1078" ]
1117	Callable with Insufficient Behavioral Summary	[]	Incomplete	Base	The code contains a function or method whose signature and/or associated inline documentation does not sufficiently describe the callable's inputs, outputs, side effects, assumptions, or return codes.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1078" ]
1118	Insufficient Documentation of Error Handling Techniques	[]	Incomplete	Base	The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[]	[ "1059" ]
1119	Excessive Use of Unconditional Branching	[]	Incomplete	Base	The code uses too many unconditional branches (such as "goto").	[]	{ "technology": null, "language": null }	[]	[]	{ "usage": "Prohibited" }	[ { "scope": "Other", "note": "" } ]	[ "1120" ]
112	Missing XML Validation	[]	Draft	Base	The product accepts XML from an untrusted source but does not validate the XML against the proper schema.	[ { "method": "Automated Static Analysis", "description": "Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect \"sources\" (origins of input) with \"sinks\" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)" } ]	{ "technology": null, "language": "Not Language-Specific" }	[ { "phase": "Implementation" } ]	[]	{ "usage": "Allowed" }	[ { "scope": "Integrity", "note": "" } ]	[ "1286", "20" ]

End of preview.

README.md exists but content is empty.

Downloads last month: 263