GHSA-jmw5-58c7-587h
LOWGHSA-jmw5-58c7-587h is a low-severity (CVSS 3.7) Deserialization of Untrusted Data vulnerability in org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socket. O3 Security confirms whether GHSA-jmw5-58c7-587h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Karaf Decanter has Deserialization of Untrusted Data in its Log Socket Collector
Blast Radius
org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socketReal-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
Deserialization of Untrusted Data vulnerability in Apache Karaf Decanter.
The Decanter Log Socket Collector exposes port 4560 without authentication. If the collector exposes allowed classes property, this configuration can be bypassed. The Log Socket Collector is vulnerable to deserialization of untrusted data, eventually causing DoS.
NB: Decanter Log Socket Collector is not installed by default. Users who have not installed the Decanter Log Socket are not impacted by this issue.
This issue affects Apache Karaf Decanter before 2.12.0.
Users are recommended to upgrade to version 2.12.0, which fixes the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socket | all versions | 2.12.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socket. 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 org.apache.karaf.decanter.collector:org.apache.karaf.decanter.collector.log.socket to 2.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmw5-58c7-587h 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-jmw5-58c7-587h 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-jmw5-58c7-587h. 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-jmw5-58c7-587h in your dependencies?
O3 detects GHSA-jmw5-58c7-587h across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.