CVE-2024-1979 is a low-severity (CVSS 3.5) Information Exposure vulnerability in io.quarkus:quarkus-kubernetes-deployment. A fix is available for io.quarkus:quarkus-kubernetes-deployment — see the affected versions and patch details below.
Quarkus: information leak in annotation
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-1979.
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
io.quarkus:quarkus-kubernetes-deploymentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in Quarkus. In certain conditions related to the CI process, git credentials could be inadvertently published, which could put the git repository at risk.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-kubernetes-deployment | all versions | 3.7.3io.quarkus:quarkus-kubernetes-deployment:3.7.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-kubernetes-deployment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-kubernetes-deployment to 3.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-1979 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Three conditions are required to enable this vulnerability: 1) If you are in an environment where you have a token in the Git URL of the Quarkus project you are building 2) If you build with a Quarkus extension that generates a Kubernetes descriptor (for instance a Kubernetes or OpenShift extension) 3) If this…
Ensure that at least one of the preconditions is not present in your environment.Source: Red Hat security advisory for CVE-2024-1979 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Quarkus 3.2.11.Final | io.quarkus/quarkus-kubernetes-deployment:3.2.11.Final-redhat-00001 | RHSA-2024:1662 |
Frequently Asked Questions
Is CVE-2024-1979 in your dependencies?
Find it across Maven, including transitive dependencies.