| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| github.com/goharbor/harbor | ≥ 2.10.0, < 2.10.2≥ 2.10.0+incompatible, < 2.10.2+incompatible≥ 2.9.0, < 2.9.4≥ 2.9.0+incompatible, < 2.9.4+incompatible< 2.8.6< 2.8.6+incompatible | 2.10.22.10.2+incompatible2.9.42.9.4+incompatible2.8.62.8.6+incompatible |
| harbor | ≥ 2.10.0, < 2.10.2≥ 2.8.1, < 2.8.6≥ 2.9.0, < 2.9.4 | 2.10.22.8.62.9.4 |
A user with an administrator, project_admin, or project_maintainer role could utilize and exploit SQL Injection to allow the execution of any Postgres function or the extraction of sensitive information from the database through this API:
GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/scan/{report_id}/log
The SQL injection might happen in the code:
Because raw SQL executed in ormer.Raw(Sql).QueryRows() is PrepareStatement. In the driver of Postgres, one PrepareStatement must contain only ONE SQL command, see https://www.postgresql.org/docs/15/libpq-exec.html#LIBPQ-PQPREPARE. The SQL should start with:
SELECT * FROM task WHERE extra_attrs::jsonb->'report_uuids' @>
Adding a delete/update operation by appending malicious content to the current SQL is impossible. Furthermore, the query result of the task is just an intermediate result, the task ID is used to locate the job log file, and the response only contains the content of the job log file. so this vulnerability can be used to execute SQL functions, but it can't leak any useful information to the response.
Harbor >=v2.8.1, >=2.9.0, >=2.10.0 are impacted.
Harbor v2.8.6, v2.9.4, v2.10.2 fixes this issue.
There is no workaround for this issue.
Thanks Taisei Inoue ([email protected])
これらの製品をお使いですか？サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン