CodeQL analysis does not detect expected command injection vulnerability
- Ngôn ngữ chính
- CodeQL
- Star
- 10.1k
- Fork
- 2.1k
- Merge trung bình
- 2 ngày 15 giờ
- Pull request đã merge (30 ngày)
- 141
Mô tả
**Hello CodeQL team**,
I'm currently integrating CodeQL into our CI workflow for an end-to-end security test of our backend system.
Here's the procedure I followed:
Setup:
**Downloaded the CLI:**
wget https://github.com/github/codeql-cli-binaries/releases/latest/download/codeql-linux64.zip
unzip codeql-linux64.zip
sudo mv codeql /usr/local/bin/
**Cloned the CodeQL repository with Python libraries:**
git clone https://github.com/github/codeql.git
**Inside the backend directory, created the database:**
codeql database create db-python --language=python --source-root=.
**Ran the analysis:**
codeql database analyze db-python codeql/python/ql/src/codeql-suites/python-lgtm-full.qls --format=sarifv2.1.0 --output=python-code-scanning-sec-all.sarif
**Checked the results:**
jq '.runs[].results[] | {message: .message.text, severity: .level, location: .locations[0].physicalLocation.artifactLocation.uri}' python-code-scanning-sec-all.sarif
**Problem**
Before running the scan, I added the following code snippet to the backend intentionally to trigger a command injection warning:
```
import os
user_input = input("Enter command: ")
os.system(user_input) # ⚠️ This should trigger a CodeQL rule: command injection
```
However, the scan results do not include any findings related to this vulnerable code.
**Question**
Am I missing something in the setup or the suite configuration?
Is there a different CodeQL query or suite that should be used to detect this specific type of vulnerability (e.g., command injection via os.system) in Python?
Any help or guidance would be much appreciated!
Best regards,
Anton
Hướng dẫn đóng góp
Hướng nghiên cứu
Reproduce the report with the shown Python snippet, the db-python database, and codeql/python/ql/src/codeql-suites/python-lgtm-full.qls. Inspect the generated python-code-scanning-sec-all.sarif results and the suite configuration to determine why no finding appears. Done means identifying the cause and documenting the required query or setup for detecting this case.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Đánh giá
- Công nghệ
- python
- Lĩnh vực
- security
- Loại issue
- Lỗi
- Độ khó
- 4/5
- Thời gian dự kiến
- 3-5 ngày
- Mức độ hoạt động
- Đình trệ
- Độ rõ ràng
- Cần làm rõ
- Mức phù hợp với người mới
- 30/100