CVE-2024-22261: SQL Injection in Harbor scan log API

Published Jun 2, 2024
·
Updated

Impact

A user with an administrator, projectadmin, or projectmaintainer 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/{projectname}/repositories/{repositoryname}/artifacts/{reference}/scan/{reportid}/log The SQL injection might happen in the code:

https://github.com/goharbor/harbor/blob/9b7c1a2274fbc5ea16e19a484532f86c08926577/src/pkg/task/task.go#L241

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 extraattrs::jsonb->'reportuuids' @> 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.

Patches Harbor v2.8.6, v2.9.4, v2.10.2 fixes this issue.

Workarounds There is no workaround for this issue.

Credits

Thanks Taisei Inoue (taisei.inoue@gmo-cybersecurity.com)

Other sources

SQL-Injection in Harbor allows priviledge users to leak the task IDs

MITRE

Affected Software

6 affected componentsFixes available
go/github.com/goharbor/harbor>=2.10.0<2.10.2
2.10.2
go/github.com/goharbor/harbor>=2.9.0<2.9.4
2.9.4
go/github.com/goharbor/harbor<2.8.6
2.8.6
linuxfoundation Harbor>=2.8.1<2.8.6
linuxfoundation Harbor>=2.9.0<2.9.4
linuxfoundation Harbor>=2.10.0<2.10.2

Event History

Jun 2, 2024
Advisory Published
via GitHub·10:32 PM
Jun 10, 2024
CVE Published
via MITRE·11:25 PM
Data Sourced
via MITRE·11:25 PM
DescriptionSeverityWeakness
Jun 11, 2024
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 AM
Affected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-22261?

CVE-2024-22261 has been identified as a high severity vulnerability due to the potential for SQL injection and unauthorized access to sensitive information.

2

How do I fix CVE-2024-22261?

To mitigate CVE-2024-22261, update your Harbor installation to version 2.10.2 or higher, 2.9.4, or ensure your version is below 2.8.6.

3

Who is affected by CVE-2024-22261?

CVE-2024-22261 affects users with administrator, project_admin, or project_maintainer roles in specific versions of Harbor.

4

What type of vulnerability is CVE-2024-22261?

CVE-2024-22261 is categorized as an SQL Injection vulnerability affecting the Harbor API.

5

What can attackers achieve with CVE-2024-22261?

Attackers exploiting CVE-2024-22261 could execute arbitrary Postgres functions or extract sensitive information from the database.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203