CVE-2022-36036

Improper Control of Generation of Code ('Code Injection') in mdx-mermaid

Arbitary javascript injection

Modify any mermaid code blocks with the following code and the code inside will execute when the component is loaded by MDXjs

` + (function () {
  // Put Javascript code here
  return ''
}()) + `

The block below shows a valid mermaid code block

```mermaid
graph TD;
    A-->B;
    A-->C;
    B-->D;
    C-->D;
```

The same block but with the exploit added

```mermaid
` + (function () {
  alert('vulnerable')
  return ''
}()) + `
graph TD;
    A-->B;
    A-->C;
    B-->D;
    C-->D;
```

Workarounds

None known

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2022-36036 has a CVSS score of 3.6 (Low). The vector is requires local access, 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 (1.3.0, 2.0.0-rc2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1.3.0 and 2.0.0-rc2

1. What is CVE-2022-36036? CVE-2022-36036 is a low-severity code injection vulnerability in mdx-mermaid (npm), affecting versions < 1.3.0. It is fixed in 1.3.0, 2.0.0-rc2. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2022-36036? CVE-2022-36036 has a CVSS score of 3.6 (Low). 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 mdx-mermaid are affected by CVE-2022-36036? mdx-mermaid (npm) versions < 1.3.0 is affected.
4. Is there a fix for CVE-2022-36036? Yes. CVE-2022-36036 is fixed in 1.3.0, 2.0.0-rc2. Upgrade to this version or later.
5. Is CVE-2022-36036 exploitable, and should I be worried? Whether CVE-2022-36036 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 CVE-2022-36036 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 CVE-2022-36036?
   • Upgrade mdx-mermaid to 1.3.0 or later
   • Upgrade mdx-mermaid to 2.0.0-rc2 or later