CVE-2022-31069 Potential Authorization Header Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy
Attackers can view sensitive OAuth tokens exposed to backend services due to missing header forwarding controls in the NestJS proxy library.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-31069?
CVE-2022-31069 is a medium-severity vulnerability in finastra-nodejs-libs, published on 15 Jun 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
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 control when Authorization headers should should be forwarded for specific backend services configured by the application developer. This could have resulted in sensitive information such as OAuth bearer access tokens being inadvertently exposed to such services that should not see them. A new feature has been introduced in the patched version of nestjs-proxy that allows application developers to opt out of forwarding the Authorization headers on a per service basis using the `forwardToken` config setting. Developers are advised to review the README for this library on Github or NPM for further details on how this configuration can be applied. 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.
Weakness: CWE-200
Which versions are affected by CVE-2022-31069?
2 open source packages ship an affected version, including @finastra/nestjs-proxy. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
@finastra/nestjs-proxy npm | All versions | 0.7.0 |
@finastra/nestjs-proxy npm | All versions | 0.7.0 |
Products include Finastra Nestjs-Proxy, Nestjs-Proxy Project Nestjs-Proxy.
How do I fix CVE-2022-31069?
Upgrade @finastra/nestjs-proxy to 0.7.0 or later.
Is CVE-2022-31069 being exploited?
There is no known exploitation of CVE-2022-31069 in the wild and no public exploit code.
Other vulnerabilities in finastra-nodejs-libs
Sources
Also known as GHSA-j562-c3cw-3p5g.