What is CVE-2022-31069?

CVE-2022-31069 is a medium-severity security vulnerability in @finastra/nestjs-proxy (npm), affecting versions < 0.7.0. It is fixed in 0.7.0.

How severe is CVE-2022-31069?

CVE-2022-31069 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @finastra/nestjs-proxy are affected by CVE-2022-31069?

@finastra/nestjs-proxy (npm) versions < 0.7.0 is affected.

Is there a fix for CVE-2022-31069?

Yes. CVE-2022-31069 is fixed in 0.7.0. Upgrade to this version or later.

Is CVE-2022-31069 exploitable, and should I be worried?

Whether CVE-2022-31069 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-31069 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-31069?

Upgrade @finastra/nestjs-proxy to 0.7.0 or later.

CVE-2022-31069 in @finastra/nestjs-proxy

Q: How severe is CVE-2022-31069?

CVE-2022-31069 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @finastra/nestjs-proxy are affected by CVE-2022-31069?

@finastra/nestjs-proxy (npm) versions < 0.7.0 is affected.

Q: Is there a fix for CVE-2022-31069?

Yes. CVE-2022-31069 is fixed in 0.7.0. Upgrade to this version or later.

Q: Is CVE-2022-31069 exploitable, and should I be worried?

Whether CVE-2022-31069 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-31069 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-31069?

Upgrade @finastra/nestjs-proxy to 0.7.0 or later.

Summary

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.

References

Impact

CVE-2022-31069 has a CVSS score of 5.8 (Medium). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.7.0); upgrading removes the vulnerable code path.

Affected versions

@finastra/nestjs-proxy (< 0.7.0)

Security releases

@finastra/nestjs-proxy → 0.7.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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. Please update your package.json file to use @finastra/nestjs-proxy instead.

Frequently Asked Questions

What is CVE-2022-31069? CVE-2022-31069 is a medium-severity security vulnerability in @finastra/nestjs-proxy (npm), affecting versions < 0.7.0. It is fixed in 0.7.0.
How severe is CVE-2022-31069? CVE-2022-31069 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @finastra/nestjs-proxy are affected by CVE-2022-31069? @finastra/nestjs-proxy (npm) versions < 0.7.0 is affected.
Is there a fix for CVE-2022-31069? Yes. CVE-2022-31069 is fixed in 0.7.0. Upgrade to this version or later.
Is CVE-2022-31069 exploitable, and should I be worried? Whether CVE-2022-31069 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-31069 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-31069? Upgrade @finastra/nestjs-proxy to 0.7.0 or later.

Other vulnerabilities in @finastra/nestjs-proxy

CVE-IDSeverityPackage summary

CVE-2022-31070Medium@finastra/nestjs-proxy: Potential Sensitive Cookie Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy