We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
You may wish to upgrade tabtab as the version 2.2.2 suffers from a regex vuln . - see here
It is resolved in tabtab v3+ by pulling in the latest debug version 4.1.0
└─ caporal:1.2.0 └─ tabtab:2.2.2 └─ debug:2.6.9
Vulnerabilities DepShield reports that this application's usage of debug:2.6.9 results in the following vulnerability(s): (CVSS 7.5) CWE-400: Uncontrolled Resource Consumption ('Resource Exhaustion') Occurrences debug:2.6.9 is a transitive dependency introduced by the following direct dependency(s): • @pact-foundation/pact:8.2.4 └─ @pact-foundation/pact-node:8.3.3 └─ caporal:1.2.0 └─ tabtab:2.2.2 └─ debug:2.6.9 └─ sumchecker:2.0.2 └─ debug:2.6.9 └─ body-parser:1.19.0 └─ debug:2.6.9 └─ express:4.17.1 └─ debug:2.6.9 └─ finalhandler:1.1.2 └─ debug:2.6.9 └─ send:0.17.1 └─ debug:2.6.9 • lint-staged:8.1.6 └─ micromatch:3.1.10 └─ extglob:2.0.4 └─ expand-brackets:2.1.4 └─ debug:2.6.9 └─ snapdragon:0.8.2 └─ debug:2.6.9
The text was updated successfully, but these errors were encountered:
On further investigation this is a non-issue as the maintainer of express app got the guys to backport the fix into 2.6.9 🥇
Sorry, something went wrong.
mattallty
No branches or pull requests
Hi,
You may wish to upgrade tabtab as the version 2.2.2 suffers from a regex vuln . - see here
It is resolved in tabtab v3+ by pulling in the latest debug version 4.1.0
The text was updated successfully, but these errors were encountered: