High, CVSS 7.1GoPublished
SQL Injection in the KubeClarity REST API
CVE-2024-39909 · GHSA-5248-h45p-9pgw
- Affected
- Go github.com/openclarity/kubeclarity/backend < 0.0.0-20240711173334-1d1178840703
- Fixed in
- 0.0.0-20240711173334-1d1178840703· Vendor fix available
- Issue
- A time/boolean SQL Injection is present in the following resource /api/applicationResources via the following parameter packageID Details As it can be seen here, while building the SQL Query the fmt.Sprintf function is used to build the query string without the input having first been subjected to any validation. PoC The following command should be able to trigger a basic version of the behavior: curl -i -s -k -X $'GET' \ -H $'Host: kubeclarity.test' \ $'https://kubeclarity.test/api/applicationResources?page=1&pageSize=50&sortKey=vulnerabilities&sortDir=DESC&packageID=c89973a6-4e7f-50b5-afe2-6bf6f4d3da0a\'HTTP/2' Impact While using the Helm chart, the impact of this vulnerability is limited since it allows read access only to the kuberclarity database, to which access is already given as far as I understand to regular users anyway. On the other hand, if Kuberclarity is deployed in a less secure way, this might allow access to more data then allowed or expected (beyond the…
Recommended action: Upgrade to 0.0.0-20240711173334-1d1178840703 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.