568
[REF-1402]"aes0_wrapper.sv". 2021. < https://github.com/HACK-EVENT/hackatdac21/
blob/65d0ffdab7426da4509c98d62e163bcce642f651/piton/design/chip/tile/ariane/src/aes0/
aes0_wrapper.sv#L84C2-L90C29> >.2024-02-14.
[REF-1403]"Fix for aes0_wrapper". 2023 November 9. < https://github.com/HACK-EVENT/
hackatdac21/blob/0034dff6852365a8c4e36590a47ea8b088d725ae/piton/design/chip/tile/ariane/
src/aes0/aes0_wrapper.sv#L96C1-L102C16 >.2024-02-14.
CWE-228: Improper Handling of Syntactically Invalid Structure
Weakness ID : 228
Structure : Simple
Abstraction : Class
Description
The product does not handle or incorrectly handles input that is not syntactically well-formed with
respect to the associated specification.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 703 Improper Check or Handling of Exceptional Conditions 1535
ChildOf 707 Improper Neutralization 1546
ParentOf 166 Improper Handling of Missing Special Element 423
ParentOf 167 Improper Handling of Additional Special Element 425
ParentOf 168 Improper Handling of Inconsistent Special Elements 426
ParentOf 229 Improper Handling of Values 570
ParentOf 233 Improper Handling of Parameters 574
ParentOf 237 Improper Handling of Structural Elements 580
ParentOf 241 Improper Handling of Unexpected Data Type 584
Common Consequences
Scope Impact Likelihood
Integrity
Availability
Unexpected State
DoS: Crash, Exit, or Restart
DoS: Resource Consumption (CPU)
If an input is syntactically invalid, then processing the input
could place the system in an unexpected state that could
lead to a crash, consume available system resources or
other unintended behaviors.
Detection Methods
Automated Static Analysis
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.)
CWE Version 4.14
CWE-228: Improper Handling of Syntactically Invalid Structure
CWE-228: Improper Handling of Syntactically Invalid Structure