CVE-2022-31070: Potential Sensitive Cookie Exposure in @finastra/nestjs-proxy, @ffdc/nestjs-proxy
Summary
CVE-2022-31070: Potential Sensitive Cookie Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy. Affects @finastra/nestjs-proxy versions < 0.7.0. Fixed in 0.7.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @finastra/nestjs-proxy and @ffdc/nestjs-proxy packages are npm packages used in Node.js applications. They provide a proxy functionality for forwarding requests to backend services. These packages allow developers to configure the proxy behavior and handle requests to external services. However, a vulnerability was discovered in these packages that could lead to the exposure of sensitive cookies to backend services that should not have access to them.
Vulnerability Detail
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 of the library now blocks cookies from being forwarded by default. Developers can configure an allow-list of cookie names to be forwarded by using the allowedCookies config setting. This vulnerability has a CVSS score of 5.8, indicating a moderate severity level.
How To Fix
Minimum fixed version
0.7.0
This is the first release that contains the fix.
npm install @finastra/nestjs-proxy@0.7.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
In conclusion, the @finastra/nestjs-proxy and @ffdc/nestjs-proxy packages had a vulnerability that could lead to the exposure of sensitive cookies to backend services. This vulnerability has been fixed in version 0.7.0 of the @finastra/nestjs-proxy package. Users of the deprecated @ffdc/nestjs-proxy package should update their package.json file to use @finastra/nestjs-proxy instead. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for @finastra/nestjs-proxy →
FAQ
The vulnerability could lead to the exposure of sensitive cookies to backend services that should not have access to them. This could potentially result in unauthorized access to user sessions or other sensitive information.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
There are no specific workarounds mentioned for this vulnerability. The recommended solution is to update to the patched version of the @finastra/nestjs-proxy package.
No, the @ffdc/nestjs-proxy package has been deprecated and is no longer maintained or receiving updates. It is recommended to update your package.json file to use @finastra/nestjs-proxy instead.
You can find more information about the fix and configuration options in the library's README on Github (https://github.com/Finastra/finastra-nodejs-libs/tree/develop/libs/proxy) or on the NPM page (https://www.npmjs.com/package/@finastra/nestjs-proxy).
References
Related vulnerabilities
Recent vulnerabilities recorded for @finastra/nestjs-proxy.
