Improper Handling of Undefined Values
CWE-232
The product does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.
We track 6 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 7.7.
Latest Improper Handling of Undefined Values vulnerabilities
- 8.6 High severity
upKeeper Instant Privilege Access: Improper Handling of Undefined Values
Improper handling of undefined values vulnerability in upKeeper Solutions upKeeper Instant Privilege Access allows Privilege Escalation. This issue affects upKeeper Instant Privilege Access: through 1.7.1.
- 7.5 High severity
BIND 9: Improper Handling of Undefined Values
When an incoming DNS protocol message includes a Transaction Signature (TSIG), BIND always checks it. If the TSIG contains an invalid value in the algorithm field, BIND immediately aborts with an assertion failure. This issue affects BIND 9 versions 9.20.0 thr
- 7.7 High severity
Cisco IOS XE Software: Improper Handling of Undefined Values
A vulnerability in the Internet Key Exchange version 1 (IKEv1) implementation of Cisco IOS XE Software could allow an authenticated, remote attacker to cause a denial of service (DoS) condition. The attacker must have valid IKEv1 VPN credentials to exploit thi
- 7.5 High severity
Routinator: Improper Handling of Undefined Values
NLnet Labs' Routinator up to and including version 0.12.1 may crash when trying to parse certain malformed RPKI objects. This is due to insufficient input checking in the bcder library covered by CVE-2023-39914.
- 7.5 High severity
bcder: Improper Handling of Undefined Values
NLnet Labs' bcder library up to and including version 0.7.2 panics while decoding certain invalid input data rather than rejecting the data with an error. This can affect both the actual decoding stage as well as accessing content of types that utilized delaye
- 7.5 High severity
Proxy: Improper Handling of Undefined Values
A remote attacker can trigger a denial of service in the socket.remoteAddress variable, by sending a crafted HTTP request. Usage of the undefined variable raises a TypeError exception.