Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-7g97-7r3c-5cc6

LOW

GHSA-7g97-7r3c-5cc6 is a low-severity (CVSS 3.5) Information Exposure vulnerability in io.quarkus:quarkus-kubernetes-deployment. O3 Security confirms whether GHSA-7g97-7r3c-5cc6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

In Quarkus, git credentials could be inadvertently published

Also known asCVE-2024-1979
Published
Mar 13, 2024
Updated
Apr 3, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk45th percentile0.00%
0.00%0.37%0.73%1.10%0.1%0.6%Feb 26Jun 26Aug 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
io.quarkus:quarkus-kubernetes-deployment

Real-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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.quarkus:quarkus-kubernetes-deploymentall versions3.7.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-kubernetes-deployment. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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 GHSA-7g97-7r3c-5cc6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7g97-7r3c-5cc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7g97-7r3c-5cc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-7g97-7r3c-5cc6 in your dependencies?

O3 detects GHSA-7g97-7r3c-5cc6 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.