GHSA-q95j-488q-5q3p — apiman-manager-api-impl
MEDIUMGHSA-q95j-488q-5q3p is a medium-severity (CVSS 6.5) vulnerability in io.apiman:apiman-manager-api-impl. A fix is available for io.apiman:apiman-manager-api-impl — see the affected versions and patch details below.
Apiman Manager API affected by Jackson denial of service vulnerability
Real-World Exposure
io.apiman:apiman-manager-api-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
Due to a vulnerability in jackson-databind <= 2.12.6.0, an authenticated attacker could craft an Apiman policy configuration which, when saved, may cause a denial of service on the Apiman Manager API.
This does not affect the Apiman Gateway.
Patches
Upgrade to Apiman 3.0.0.Final or later.
If you are using an older version of Apiman and need to remain on that version, contact your Apiman support provider for advice/long-term support.
Workarounds
If all users of the Apiman Manager are trusted then you may assess this is low risk, as an account is required to exploit the vulnerability.
References
- Apiman maintainer and security contact: [email protected]
- https://nvd.nist.gov/vuln/detail/CVE-2020-36518
- https://github.com/FasterXML/jackson-databind/issues/2816
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.apiman:apiman-manager-api-impl | all versions | 3.0.0.Finalio.apiman:apiman-manager-api-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-impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.apiman:apiman-manager-api-impl to 3.0.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q95j-488q-5q3p 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-q95j-488q-5q3p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-q95j-488q-5q3p. 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-q95j-488q-5q3p in your dependencies?
O3 Security finds GHSA-q95j-488q-5q3p across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.