Closed sjkummer closed 10 months ago
It looks like the inline-css
and extract-css
do not have a fix for this. The closest dependency to pac-resolver
in the chain that provides a fix is superagent-proxy@3.0.0
.
https://nvd.nist.gov/vuln/detail/CVE-2021-23406
It seems like forcing degenerator@3.0.1
using npm-force-resolutions
is a viable workaround.
EDIT: nevermind, only vulnerable versions of degenerator seem to be compatible with nest mailer
Besides pac-resolver
and degenerator
, inline-css
brings 2 other packages with security issues: css-what
and nth-check
.
See:
Perhaps a better strategy would be to have inline-css as an optional dependency? It also seems to bring with it an incredibly amount of dependencies, which would be nice to avoid if you don't want to use that feature.