gatsby-plugin-mdx@1.0.25 vulnerabilities

MDX integration for Gatsby

  • latest version

    5.14.0

  • latest non vulnerable version

  • first published

    6 years ago

  • latest version published

    1 months ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the gatsby-plugin-mdx package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Information Exposure

    gatsby-plugin-mdx is a MDX integration for Gatsby

    Affected versions of this package are vulnerable to Information Exposure via local file inclusion in __file-code-frame or __original-stack-frame, when gatsby develop is in use and exposed to the internet.

    NOTE: By default gatsby develop is only accessible via the localhost 127.0.0.1, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as --host 0.0.0.0, -H 0.0.0.0, or the GATSBY_HOST=0.0.0.0 environment variable.

    How to fix Information Exposure?

    Upgrade gatsby-plugin-mdx to version 5.10.0 or higher.

    <5.10.0
    • H
    Deserialization of Untrusted Data

    gatsby-plugin-mdx is a MDX integration for Gatsby

    Affected versions of this package are vulnerable to Deserialization of Untrusted Data when passing input through to the gray-matter package, due to its default configurations that are missing input sanitization. Exploiting this vulnerability is possible when passing input in both webpack (MDX files in src/pages or MDX file imported as a component in frontend / React code) and data mode (querying MDX nodes via GraphQL).

    How to fix Deserialization of Untrusted Data?

    Upgrade gatsby-plugin-mdx to version 2.14.1, 3.15.2 or higher.

    <2.14.1>=3.0.0 <3.15.2