Use of Incorrect Operator
CWE-480
The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.
We track 6 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.2.
Latest Use of Incorrect Operator vulnerabilities
- 7.3 High severity
Secure Connect Gateway 5.0 - Application: Use of Incorrect Operator
Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains an Use of Incorrect Operator vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, lea
- 7.5 High severity
Keystone is a content management system for Node.js.
Keystone is a content management system for Node.js. Prior to 6.5.3, the findMany resolver in packages/core/src/lib/core/queries/resolvers.ts compares the signed take argument directly with graphql.maxTake, allowing a remote unauthenticated GraphQL client to p
- 9.8 Critical severity
DBI::SQL::Nano: Use of Incorrect Operator
DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted <= and >= SQL operators on text. DBI::SQL::Nano, DBI's built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched meth
- 7.5 High severity
envoy: Use of Incorrect Operator
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to 1.35.11, 1.36.7, 1.37.3, and 1.38.1, in cases where UDP DNS filter is configured with local resolution containing a name with the length of 255 octets or remote res
- 9.4 Critical severity
In the Linux kernel, the following vulnerability has been resolved: netfilter…
In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry New test case fails unexpectedly when avx2 matching functions are used. The test first loads a ranomly generated pipap
- 7.5 High severity
FreeBSD: Use of Incorrect Operator
A regression in the way hashes were calculated caused rules containing the address range syntax (x.x.x.x - y.y.y.y) that only differ in the address range(s) involved to be silently dropped as duplicates. Only the first of such rules is actually loaded into pf.