SQL Injection in the KubeClarity REST API
cve-program · CVE-2024-39909
PublishedKubeClarity is a tool for detection and management of Software Bill Of Materials (SBOM) and vulnerabilities of container images and filesystems. A time/boolean SQL Injection is present in the following resource `/api/applicationResources` via the following parameter `packageID`. As it can be seen in backend/pkg/database/id_view.go, 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. This vulnerability is fixed in 2.23.1.
Read the publisher's advisoryeuvd · EUVD-2024-2252
PublishedKubeClarity is a tool for detection and management of Software Bill Of Materials (SBOM) and vulnerabilities of container images and filesystems. A time/boolean SQL Injection is present in the following resource `/api/applicationResources` via the following parameter `packageID`. As it can be seen in backend/pkg/database/id_view.go, 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. This vulnerability is fixed in 2.23.1.
Read the publisher's advisorynvd · CVE-2024-39909
PublishedKubeClarity is a tool for detection and management of Software Bill Of Materials (SBOM) and vulnerabilities of container images and filesystems. A time/boolean SQL Injection is present in the following resource `/api/applicationResources` via the following parameter `packageID`. As it can be seen in backend/pkg/database/id_view.go, 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. This vulnerability is fixed in 2.23.1.
Read the publisher's advisoryosv · GHSA-5248-h45p-9pgw
Published### Summary 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](https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79), 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 limits of the KuberClarity database). The vulnerable line was introduced as part of the initial commit of Kubeclarity, so all versions up until the latest (2.23.1) are assumed vulnerable.
Read the publisher's advisoryosv · GO-2024-2981
PublishedSQL Injection in the KubeClarity REST API in github.com/openclarity/kubeclarity/backend
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-39909 · CVE overview and exploitation status
cve-program · CVE-2024-39909
- https://github.com/openclarity/kubeclarity/security/advisories/GHSA-5248-h45p-9pgw
- https://github.com/openclarity/kubeclarity/commit/1d1178840703a72d9082b7fc4aea0a3326c5d294
- https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79
euvd · EUVD-2024-2252
- https://github.com/openclarity/kubeclarity/security/advisories/GHSA-5248-h45p-9pgw
- https://github.com/openclarity/kubeclarity/commit/1d1178840703a72d9082b7fc4aea0a3326c5d294
- https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79
nvd · CVE-2024-39909
- https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79
- https://github.com/openclarity/kubeclarity/commit/1d1178840703a72d9082b7fc4aea0a3326c5d294
- https://github.com/openclarity/kubeclarity/security/advisories/GHSA-5248-h45p-9pgw
osv · GHSA-5248-h45p-9pgw
- https://github.com/openclarity/kubeclarity/security/advisories/GHSA-5248-h45p-9pgw
- https://nvd.nist.gov/vuln/detail/CVE-2024-39909
- https://github.com/openclarity/kubeclarity/commit/1d1178840703a72d9082b7fc4aea0a3326c5d294
- https://github.com/openclarity/kubeclarity
- https://github.com/openclarity/kubeclarity/blob/main/backend/pkg/database/id_view.go#L79
osv · GO-2024-2981
Related changes
Linked by CVE identifierNo related changes are available here.