Homepage

ejs@0.0.4 vulnerabilities

Embedded JavaScript templates

  • latest version

    3.1.10

  • latest non vulnerable version

    3.1.10

  • first published

    14 years ago

  • latest version published

    11 months ago

  • licenses detected

  • View ejs package health on Snyk Advisor  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the ejs 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
    Improper Control of Dynamically-Managed Code Resources

    ejs is a popular JavaScript templating engine.

    Affected versions of this package are vulnerable to Improper Control of Dynamically-Managed Code Resources due to the lack of certain pollution protection mechanisms. An attacker can exploit this vulnerability to manipulate object properties that should not be accessible or modifiable.

    Note:

    Even after updating to the fix version that adds enhanced protection against prototype pollution, it is still possible to override the hasOwnProperty method.

    How to fix Improper Control of Dynamically-Managed Code Resources?

    Upgrade ejs to version 3.1.10 or higher.

    <3.1.10
    • H
    Remote Code Execution (RCE)

    ejs is a popular JavaScript templating engine.

    Affected versions of this package are vulnerable to Remote Code Execution (RCE) by passing an unrestricted render option via the view options parameter of renderFile, which makes it possible to inject code into outputFunctionName.

    Note: This vulnerability is exploitable only if the server is already vulnerable to Prototype Pollution.

    How to fix Remote Code Execution (RCE)?

    Upgrade ejs to version 3.1.7 or higher.

    <3.1.7
    • M
    Arbitrary Code Injection

    ejs is a popular JavaScript templating engine.

    Affected versions of this package are vulnerable to Arbitrary Code Injection via the render and renderFile. If external input is flowing into the options parameter, an attacker is able run arbitrary code. This include the filename, compileDebug, and client option.

    How to fix Arbitrary Code Injection?

    Upgrade ejs to version 3.1.6 or higher.

    <3.1.6
    • M
    Cross-site Scripting (XSS)

    ejs is a popular JavaScript templating engine. Affected versions of the package are vulnerable to Cross-site Scripting by letting the attacker under certain conditions control and override the filename option causing it to render the value as is, without escaping it. You can read more about this vulnerability on the Snyk blog.

    There's also a Remote Code Execution & Denial of Service vulnerabilities caused by the same behaviour.

    How to fix Cross-site Scripting (XSS)?

    The vulnerability can be resolved by either using the GitHub integration to generate a pull-request from your dashboard or by running snyk wizard from the command-line interface. Otherwise, Upgrade ejs to version 2.5.5 or higher.

    <2.5.5
    • M
    Denial of Service (DoS)

    ejs is a popular JavaScript templating engine. Affected versions of the package are vulnerable to Denial of Service by letting the attacker under certain conditions control and override the localNames option causing it to crash. You can read more about this vulnerability on the Snyk blog.

    There's also a Remote Code Execution & Cross-site Scripting vulnerabilities caused by the same behaviour.

    How to fix Denial of Service (DoS)?

    The vulnerability can be resolved by either using the GitHub integration to generate a pull-request from your dashboard or by running snyk wizard from the command-line interface. Otherwise, Upgrade ejs to version 2.5.5 or higher.

    <2.5.5
    • H
    Arbitrary Code Execution

    ejs is a popular JavaScript templating engine. Affected versions of the package are vulnerable to Remote Code Execution by letting the attacker under certain conditions control the source folder from which the engine renders include files. You can read more about this vulnerability on the Snyk blog.

    There's also a Cross-site Scripting & Denial of Service vulnerabilities caused by the same behaviour.

    How to fix Arbitrary Code Execution?

    The vulnerability can be resolved by either using the GitHub integration to generate a pull-request from your dashboard or by running snyk wizard from the command-line interface. Otherwise, Upgrade ejs to version 2.5.3 or higher.

    <2.5.3
    Go back to all versions of this package