GHSA-j94p-hv25-rm5g — apiman-manager-api-rest-i…
HIGHGHSA-j94p-hv25-rm5g is a high-severity (CVSS 7.1) Incorrect Default Permissions vulnerability in io.apiman:apiman-manager-api-rest-impl. A fix is available for io.apiman:apiman-manager-api-rest-impl — see the affected versions and patch details below.
Apiman has potential permissions bypass
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j94p-hv25-rm5g.
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.
How urgent is this, really
GHSA-j94p-hv25-rm5g plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.apiman:apiman-manager-api-rest-implReal-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
Impact
Incorrect default permissions for certain read-only resources in the Apiman 1.5.7.Final through 2.2.3.Final in the Apiman Manager REST API allows a remote authenticated attacker to access information and resources in an Apiman Organizations they are not a member of and/or do not have permissions for.
For example, an attacker may be able to craft an HTTP request to discover APIs that are private to organizations they are not members of, via fuzzing, search, and other similar mechanisms.
If the attacker has sufficient permissions in their own organization, they may also be able to sign up to the private APIs they have discovered by crafting a tailored HTTP request, thereby gaining access to an API Management protected resource that they should have access to.
-
A malicious account-holder may be able to see information about APIs they do not have permission for.
-
A malicious account-holder may be able to sign up to APIs they do not have permission for, and hence access API Management-protected resources they are not authorized to access.
-
This does NOT relate to the Apiman Gateway.
Patches
-
Upgrade to Apiman 3.0.0.Final (or later). The issue is fixed in this version.
-
If you are using an older version of Apiman, contact to your Apiman support provider for advice/long-term support.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.apiman:apiman-manager-api-rest-impl | ≥ 1.5.7&&< 3.0.0.Final | 3.0.0.Finalio.apiman:apiman-manager-api-rest-impl:3.0.0.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.apiman:apiman-manager-api-rest-impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.apiman:apiman-manager-api-rest-impl to 3.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j94p-hv25-rm5g 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j94p-hv25-rm5g can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j94p-hv25-rm5g. 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-j94p-hv25-rm5g in your dependencies?
O3 Security finds GHSA-j94p-hv25-rm5g across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.