GHSA-vh64-54px-qgf8
HIGHGoroutine Leak in Abacus SSE Implementation
EPSS Exploitation Probability
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
github.com/jasonlovesdoggo/abacusReal-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
Goroutine Leak in Abacus SSE Implementation
Summary
A critical goroutine leak vulnerability has been identified in the Abacus server's Server-Sent Events (SSE) implementation. The issue occurs when clients disconnect from the /stream endpoint, as the server fails to properly clean up resources and terminate associated goroutines. This leads to resource exhaustion where the server continues running but eventually stops accepting new SSE connections while maintaining high memory usage. The vulnerability specifically involves improper channel cleanup in the event handling mechanism, causing goroutines to remain blocked indefinitely.
POC
Impact
This vulnerability affects all versions of Abacus prior to v1.4.0. The issue causes:
- Permanent unresponsiveness of the
/streamendpoint after prolonged use - Memory growth that stabilizes at a high level but prevents proper functionality
- Selective denial of service affecting only SSE connections while other endpoints remain functional
- Accumulated orphaned goroutines that cannot be garbage collected
- High resource consumption under sustained client connection/disconnection patterns
Systems running Abacus in production with client applications that frequently establish and terminate SSE connections are most vulnerable. The issue becomes particularly apparent in high-traffic environments or during connection stress testing.
Patches
The vulnerability has been patched in Abacus v1.4.0. The fix includes:
- Implementing buffered channels to prevent blocking operations during cleanup
- Adding proper mutex-protected cleanup logic to ensure resources are released exactly once
- Implementing timeout protection for channel operations to prevent deadlocks
- Ensuring consistent cleanup when connections terminate unexpectedly
- Adding improved monitoring for client disconnections using request context
- Restructuring the event broadcasting system to safely handle client removal
Users should upgrade to v1.4.0 or later versions as soon as possible.
Workarounds
If upgrading is not immediately possible, the following workarounds can help mitigate the issue:
-
Limit maximum connections: Configure your reverse proxy to limit the maximum number of concurrent connections to the
/streamendpoints. -
Implement request timeouts: Configure your infrastructure to terminate long-lived SSE connections after a reasonable period.
-
Restart regularly: Schedule regular restarts of the Abacus service to reclaim resources.
-
Monitor memory usage: Set up alerts for abnormal memory growth patterns.
-
Separate instance for SSE: Run a dedicated Abacus instance solely for handling SSE connections, allowing it to be restarted without affecting the main API functionality.
References
- Go Concurrency Patterns: Context
- CWE-772: Missing Release of Resource after Effective Lifetime
- OWASP Top 10: Resource Exhaustion
- Resource Management in Go
For More Information
Please contact the Abacus security team at [email protected] for additional information or to report further security issues.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/jasonlovesdoggo/abacus | all versions | 0.0.0-20250302043802-898ff1204e11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jasonlovesdoggo/abacus. 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.
Fix
Update github.com/jasonlovesdoggo/abacus to 0.0.0-20250302043802-898ff1204e11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vh64-54px-qgf8 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-vh64-54px-qgf8 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-vh64-54px-qgf8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vh64-54px-qgf8 in your dependencies?
O3 detects GHSA-vh64-54px-qgf8 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.