- What is CWE-194?
- The product performs an operation on a number that causes it to be sign extended when it is transformed into a larger data type. When the original number is negative, this can produce unexpected values that lead to resultant weaknesses.
- What CVEs are caused by CWE-194?
- 5 recorded CVEs are attributed to CWE-194, including CVE-2022-32138, CVE-2018-10887, CVE-2021-38434.
- How do you prevent CWE-194?
- Avoid using signed variables if you don't need to represent negative values. When negative values are needed, perform validation after you save those values to larger data types, or before passing them to functions that are expecting unsigned values.
- How is CWE-194 detected?
- 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.)
- What are the consequences of CWE-194?
- Exploiting CWE-194 can lead to: Read Memory, Modify Memory, Other.
- Is CWE-194 actively exploited?
- 5 recorded CVEs are caused by CWE-194; none are currently in CISA's KEV catalog of actively exploited flaws.
