Improper Use of Validation Framework
CWE-1173
The product does not use, or incorrectly uses, an input validation framework that is provided by the source language, framework, or an independent library.
We track 4 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.9.
How this weakness is prevented
- Implementation: Properly use provided input validation frameworks.
Latest Improper Use of Validation Framework vulnerabilities
- 9.4 Critical severity
Apache Camel: Deserialization of Untrusted Data
The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direc
- 9.8 Critical severity
Niagara Framework: Improper Use of Validation Framework
Improper Use of Validation Framework vulnerability in Tridium Niagara Framework on Windows, Linux, QNX, Tridium Niagara Enterprise Security on Windows, Linux, QNX allows Input Data Manipulation. This issue affects Niagara Framework: before 4.14.2, before 4.15.
- 7.5 High severity
Exynos 5300 Firmware: Out-of-bounds Write
An issue was discovered in Samsung Exynos Mobile Processor, Automotive Processor and Modem for Exynos Modem 5123, Exynos Modem 5300, Exynos 980, Exynos 1080, Exynos 9110, and Exynos Auto T5123. Memory corruption can occur due to insufficient parameter validati
- 8.8 High severity
3scale API Management 2 does not perform adequate sanitation for user input in multiple fields.
3scale API Management 2 does not perform adequate sanitation for user input in multiple fields. An authenticated user could use this flaw to inject scripts and possibly gain access to sensitive information or conduct further attacks.