False Negative: CompareIdenticalValues.ql misses self-comparisons once the same value is routed through aliases or tiny helper methods.
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Comienza con Likely Bugs/Comparison/CompareIdenticalValues.ql y luego revisa PosCase2_Var1.java, PosCase2_Var3.java y PosCase3_Var3.java para comprender los casos reportados de alias, métodos auxiliares y expresiones repetidas. El trabajo estará completo cuando el checker reconozca las comparaciones indicadas como redundantes o sospechosas sin cambiar ningún otro comportamiento.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Version
codeql 2.24.3
Checker
- Checker id:
Likely Bugs/Comparison/CompareIdenticalValues.ql - Checker description: Detects comparisons where the left and right operands are identical in value, such as comparing the same variable, literal, or structurally equal expressions.
Description of the false negative
All three samples are still comparing a value against itself. The only differences are that the value is first copied through an alias or passed through a helper method that preserves the same expression on both sides.
That should still be enough for Likely Bugs/Comparison/CompareIdenticalValues.ql to report the comparison as redundant or suspicious.
Affected test cases
PosCase2_Var1.java
y != x, ref == obj, and val >= h.value all compare equivalent values. The aliasing changes syntax, not semantics.
// Comparison with identical variable accesses should be flagged as identical operands.
package scensct.var.pos;
public class PosCase2_Var1 {
public static void main(String[] args) {
int x = 10;
int y = x; // alias
boolean b1 = y != x; // still same variable value
Object obj = new Object();
Object ref = obj;
boolean b2 = ref == obj; // same reference
Holder h = new Holder();
int val = h.value;
boolean b3 = val >= h.value; // same field value
}
static class Holder {
int value = 5;
}
}
PosCase2_Var3.java
The helper calls receive identical arguments on both sides of the comparison, so the resulting expressions are still identical.
// Comparison with identical variable accesses should be flagged as identical operands.
package scensct.var.pos;
public class PosCase2_Var3 {
public static void main(String[] args) {
int x = 10;
boolean b1 = compareNotEqual(x, x);
Object obj = new Object();
boolean b2 = compareEqual(obj, obj);
Holder h = new Holder();
boolean b3 = compareGreaterOrEqual(h.value, h.value);
}
static boolean compareNotEqual(int a, int b) {
return a != b;
}
static boolean compareEqual(Object a, Object b) {
return a == b;
}
static boolean compareGreaterOrEqual(int a, int b) {
return a >= b;
}
static class Holder {
int value = 5;
}
}
PosCase3_Var3.java
Each comparison applies the same pure helper to the same inputs on both sides. That is still a self-comparison.
// Comparison with structurally identical binary expressions should be flagged as identical operands.
package scensct.var.pos;
public class PosCase3_Var3 {
// Variant 3: Extract identical expressions to a helper method
private static int addOne(int n) {
return n + 1;
}
private static int multiply(int m, int n) {
return m * n;
}
private static int subtractTwo(int n) {
return n - 2;
}
public static void main(String[] args) {
int x = 5;
int a = 2, b = 3;
boolean b1 = addOne(x) > addOne(x);
boolean b2 = multiply(a, b) == multiply(a, b);
boolean b3 = subtractTwo(x) <= subtractTwo(x);
}
}
Cause analysis
The misses suggest that Likely Bugs/Comparison/CompareIdenticalValues.ql is reasoning mostly at the surface-expression level. Once the same value is routed through a local alias or a small pure helper, the query stops recognizing that both sides of the comparison are still equivalent.
For developers, these are not edge cases. Aliases and tiny wrappers are common, and they do not make a self-comparison any less suspicious.
- Lenguaje dominante
- CodeQL
- Estrellas
- 10.1k
- Forks
- 2.1k
- Merge medio
- 2 d 16 h
- PR fusionados (30 d)
- 143
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/codeql
-
agentic-workflows
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
false-positive javascript
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
C#: cs/simplifiable-boolean-expression false positive on Nullable<bool> compared with a literal Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
false-positive
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Todos los issues de github/codeql
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
punkpeye/mcp-remote#369 ·
-
Mend: dependency security vulnerability untriaged
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
CVE-2024-24786 CPE mismatch Abiertobug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
cisagov/vulnrichment#337 ·
-
bug DUP Reservations
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
bcgov/reserve-rec-public#896 ·