Java: static field access of unknown class breaks dataflow (build-mode=none)
- 主要言語
- CodeQL
- スター
- 10.1k
- フォーク
- 2.1k
- 平均マージ
- 2日 15時間
- マージ済み PR(30日)
- 141
説明
This is another issue we encountered when analysing databases created with `build-mode=none`.
It appears that dataflow graphs are broken when static fields are accessed on unknown classes.
Please take a look [codeql_issue2.zip](https://github.com/user-attachments/files/20458091/codeql_issue2.zip) for more information.
Here is the example java code:
```
// This import is from a dependency that is not resolved
import com.foo.mycompany.UnknownClass;
public class DataFlowNotConnected {
static class MyClass {
public static String staticField = "static";
}
private int run() {
// data source 1 should flow to sink e and f, but dataflow is broken by UnknownClass.staticField
int a = 1;
int b = a;
// static class field access from known class
String staticField1 = MyClass.staticField;
int c = b;
int d = c;
// static class field access from unknown class breaks dataflow
String staticField2 = UnknownClass.staticField;
int e = d;
int f = e;
return f;
}
}
```
コントリビューションガイド
調査の方向性
Start by reproducing the example from codeql_issue2.zip with build-mode=none, focusing on the Java dataflow graph around UnknownClass.staticField. Compare the graph with and without that static access; done means the flow from a through d remains connected to sinks e and f.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- java
- 領域
- devtools, security
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 35/100