GHSA-Q95J-488Q-5Q3P

Apiman Manager API affected by Jackson denial of service vulnerability

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

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.

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

GHSA-Q95J-488Q-5Q3P has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.0.Final); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is GHSA-Q95J-488Q-5Q3P? GHSA-Q95J-488Q-5Q3P is a medium-severity out-of-bounds write vulnerability in io.apiman:apiman-manager-api-impl (maven), affecting versions <= 2.2.3.Final. It is fixed in 3.0.0.Final. A write operation targets a memory location beyond the intended buffer boundary.
2. How severe is GHSA-Q95J-488Q-5Q3P? GHSA-Q95J-488Q-5Q3P has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of io.apiman:apiman-manager-api-impl are affected by GHSA-Q95J-488Q-5Q3P? io.apiman:apiman-manager-api-impl (maven) versions <= 2.2.3.Final is affected.
4. Is there a fix for GHSA-Q95J-488Q-5Q3P? Yes. GHSA-Q95J-488Q-5Q3P is fixed in 3.0.0.Final. Upgrade to this version or later.
5. Is GHSA-Q95J-488Q-5Q3P exploitable, and should I be worried? Whether GHSA-Q95J-488Q-5Q3P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-Q95J-488Q-5Q3P is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-Q95J-488Q-5Q3P? Upgrade io.apiman:apiman-manager-api-impl to 3.0.0.Final or later.