CVE-2022-31069 is a medium-severity (CVSS 5.8) Information Exposure vulnerability in @finastra/nestjs-proxy. A fix is available for @finastra/nestjs-proxy — see the affected versions and patch details below.
Potential Authorization Header Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31069.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@finastra/nestjs-proxynpmDescription
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
- This issue has been fixed in version 0.7.0 of
@finastra/nestjs-proxy. - Users of
@ffdc/nestjs-proxyare 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-proxyinstead.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @finastra/nestjs-proxy | all versions | 0.7.0npm install @finastra/nestjs-proxy@0.7.0 |
Affected Products
nestjs-proxyfinastranestjs-proxynestjs-proxy_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @finastra/nestjs-proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @finastra/nestjs-proxy to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31069 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2022-31069 in your dependencies?
Find it across npm, including transitive dependencies.