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

GHSA-pr38-qpxm-g88x

HIGHFix: apache/activemq-artemis#3862

GHSA-pr38-qpxm-g88x is a high-severity (CVSS 7.5) CWE-770 vulnerability in org.apache.activemq:artemis-core-client. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-pr38-qpxm-g88x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache ActiveMQ Artemis Uncontrolled Resource Consumption (DoS)

Also known asCVE-2022-23913
Published
Feb 6, 2022
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Real-World Exposure

1 pkg affected
org.apache.activemq:artemis-core-client

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

In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could partially disrupt availability (DoS) through uncontrolled resource consumption of memory.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.activemq:artemis-core-clientall versions2.19.1
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.activemq:artemis-core-client. 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 org.apache.activemq:artemis-core-client to 2.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pr38-qpxm-g88x 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-pr38-qpxm-g88x 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-pr38-qpxm-g88x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could partially disrupt availability (DoS) through uncontrolled resource consumption of memory.
O3 Security · Impact-Aware SCA

Is GHSA-pr38-qpxm-g88x in your dependencies?

O3 detects GHSA-pr38-qpxm-g88x across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.