CVE-2022-31070: Potential Sensitive Cookie Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy
NestJS Proxy is a NestJS module to decorate and proxy calls. Prior to version 0.7.0, the nestjs-proxy library did not have a way to block sensitive cookies (e.g. session cookies) from being forwarded to backend services configured by the application developer. This could have led to sensitive cookies being inadvertently exposed to such services that should not see them. The patched version now blocks cookies from being forwarded by default. However developers can configure an allow-list of cookie names by using the allowedCookies config setting. This issue has been fixed in version 0.7.0 of @finastra/nestjs-proxy. Users of @ffdc/nestjs-proxy are advised that this package has been deprecated and is no longer being maintained or receiving updates. Such users should update their package.json file to use @finastra/nestjs-proxy instead.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2022-31070?
CVE-2022-31070 has a moderate severity rating due to the risk of sensitive cookies being improperly forwarded.
How do I fix CVE-2022-31070?
To fix CVE-2022-31070, upgrade to version 0.7.0 or later of the nestjs-proxy library.
What types of cookies are affected by CVE-2022-31070?
CVE-2022-31070 affects sensitive cookies such as session cookies that can be forwarded to backend services.
Which versions of nestjs-proxy are vulnerable to CVE-2022-31070?
Versions of nestjs-proxy prior to 0.7.0 and up to 0.4.0 are vulnerable to CVE-2022-31070.
Is CVE-2022-31070 exploited in the wild?
As of now, there is no public evidence indicating that CVE-2022-31070 is actively exploited in the wild.