SQL Injection in the KubeClarity REST APIGHSA-5248-h45p-9pgw
MEDIUMFix: openclarity/kubeclarity@1d11788GHSA-5248-h45p-9pgw is a medium-severity (CVSS 6.5) SQL Injection vulnerability in github.com/openclarity/kubeclarity/backend. A fix is available for github.com/openclarity/kubeclarity/backend — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-5248-h45p-9pgw.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/openclarity/kubeclarity/backendReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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, 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openclarity/kubeclarity/backend | all versions | 0.0.0-20240711173334-1d1178840703go get github.com/openclarity/kubeclarity/backend@v0.0.0-20240711173334-1d1178840703 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openclarity/kubeclarity/backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openclarity/kubeclarity/backend to 0.0.0-20240711173334-1d1178840703 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5248-h45p-9pgw is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is GHSA-5248-h45p-9pgw in your dependencies?
Find it across Go, including transitive dependencies.