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

GHSA-ggp5-28x4-xcj9

MEDIUM

Minder GetRepositoryByName data leak

Also known asCVE-2024-31455GO-2024-2701
Published
Apr 9, 2024
Updated
Jun 4, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk51th percentile+0.32%
0.00%0.42%0.84%1.26%0.3%0.8%Dec 25Apr 26Jun 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
🐹github.com/stacklok/minder

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

Impact

A recent refactoring added the ability to get GitHub repositories registered to a project without specifying a specific provider. Unfortunately, the SQL query for doing so was missing parenthesis, and would select a random repository.

Patches

Patched in #2941

Workarounds

Revert prior to 5c381cf, or roll forward past 2eb94e7

References

N/A

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/stacklok/minder0.0.39&&< 0.0.400.0.40

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/stacklok/minder. 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 github.com/stacklok/minder to 0.0.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ggp5-28x4-xcj9 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-ggp5-28x4-xcj9 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-ggp5-28x4-xcj9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A recent refactoring added the ability to get GitHub repositories registered to a project without specifying a specific provider. Unfortunately, the SQL query for doing so was missing parenthesis, and would select a random repository. ### Patches Patched in #2941 ### Workarounds Revert prior to `5c381cf`, or roll forward past `2eb94e7` ### References N/A
O3 Security · Impact-Aware SCA

Is GHSA-ggp5-28x4-xcj9 in your dependencies?

O3 detects GHSA-ggp5-28x4-xcj9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.