🚀 Big News: Socket Acquires Coana to Bring Reachability Analysis to Every Appsec Team.Learn more
Socket
DemoInstallSign in
Socket

eslint-plugin-vuln-regex-detector

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

eslint-plugin-vuln-regex-detector

Detect vulnerable regexes using the vuln-regex-detector module.

1.0.4
latest
npm
Version published
Weekly downloads
79
3.95%
Maintainers
1
Weekly downloads
 
Created
Source

eslint-plugin-vuln-regex-detector

Detect unsafe regexes.

This plugin is not intended for use with your typical eslint runs. It uses the eslint framework to identify the files you care about and to have easy access to an AST from which to extract regexes.

It does work with as part of a regular eslint configuration. However, it will be slow the first few times eslint is triggered until the local cache warms up.

So, how should you use it? I suggest adding this line to the scripts section of your package.json:

"test:regex": "eslint --plugin vuln-regex-detector --rule '\"vuln-regex-detector/no-vuln-regex\": 2' FILES_YOU_CARE_ABOUT",

Then when you run npm run test:regex, you'll run your existing eslint rules plus identify vulnerable regexes in your code. This is appropriate for use in your CI.

You should re-use your existing eslint invocation (see the lint line in your package.json scripts). You might want to restrict the files you care about, since e.g. vulnerable regexes in test/ are probably not an issue.

Configuring

The vuln-regex-detector module lets users specify the server hostname and port, as well as the local cache.

Server config

Invoke eslint with ESLINT_PLUGIN_NO_VULN_REGEX_HOSTNAME=... ESLINT_PLUGIN_NO_VULN_REGEX_PORT=....

Cache config

Invoke eslint with ESLINT_PLUGIN_NO_VULN_REGEX_PERSISTENT_DIR=....

Performance

Cold cache

From an AWS micro instance, it takes about 30 seconds to scan a project with 100 regexes.

Steady-state

This plugin relies on vuln-regex-detector which queries a remote server about regexes. Once the server gives a firm response (it might say "unknown" for a few minutes), it gets cached locally in the FS. So after a few uses on the same machine, the plugin's performance will improve. The improvement will be significant if you have many regexes.

Installation

You'll first need to install ESLint:

$ npm i eslint --save-dev

Next, install eslint-plugin-vuln-regex-detector:

$ npm install eslint-plugin-vuln-regex-detector --save-dev

Note: If you installed ESLint globally (using the -g flag) then you must also install eslint-plugin-vuln-regex-detector globally.

Usage

If you want to use it in every eslint run, update your .eslintrc configuration file as follows:

  • Update plugins.
{
    "plugins": [
        "vuln-regex-detector"
    ]
}
  • Update rules.
{
    "rules": {
        "vuln-regex-detector/no-vuln-regex": 2
    }
}

Supported Rules

  • no-vuln-regex: Identify vulnerable regexes in your code.

Keywords

eslint

FAQs

Package last updated on 07 Apr 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts