@finastra/nestjs-proxy
Affected
- introduced
0, fixed0.7.0(semver)
Fixed versions
0.7.0
Fix
- Fixed version
0.7.0npm install @finastra/[email protected]
Advisory
Also known as: CVE-2022-31069
Potential Authorization Header Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy
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.
Patches
@finastra/nestjs-proxy.@ffdc/nestjs-proxy are advised that this package has been deprecated and is no longer being maintained or receiving updates. Please update your package.json file to use @finastra/nestjs-proxy instead.References
Medium Basis: The source's own band: MODERATE
0, fixed 0.7.0 (semver)0.7.0
0.7.0npm install @finastra/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0