SQL Injection in the KubeClarity REST API

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-39909: 0.44% estimated exploitation activity in the next 30 days; percentile 38.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

12 Jul 2024, 13:56 UTC

Last modified by the source

18 Nov 2024, 16:26 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5248-h45p-9pgw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-39909

Advisory: SQL Injection in the KubeClarity REST API
IDs: CVE-2024-39909, GHSA-5248-h45p-9pgw
Record: https://patchnext.com/advisories/cve-2024-39909 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/openclarity/kubeclarity/backend 0.0.0-20240711173334-1d1178840703. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/openclarity/kubeclarity/backend: affected < 0.0.0-20240711173334-1d1178840703; fixed in 0.0.0-20240711173334-1d1178840703

## Suggested inspection (read-only)
- Go github.com/openclarity/kubeclarity/backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/openclarity/kubeclarity/backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5248-h45p-9pgw (GitHub-reviewed advisory GHSA-5248-h45p-9pgw lists affected ranges: Go github.com/openclarity/kubeclarity/backend >=0 <0.0.0-20240711173334-1d1178840703)

Commands are suggestions: review each one before running it.