CVE-2022-31069: @finastra/nestjs proxy Potential Authorization Header Exposure Vulnerability
MODERATECVE-2022-31069 is a MODERATE (CVSS 5.8) potential authorization header exposure vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting @finastra/nestjs proxy libraries in the npm ecosystem. The issue involves potential authorization header exposure in npm packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy. Remediation is available by upgrading affected packages to version 0.7.0.
CVE-2022-31069 at a Glance
Security Impact
CVSS: 5.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N).
How to Fix CVE-2022-31069
To remediate this vulnerability, upgrade all affected @finastra/nestjs proxy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @finastra/nestjs-proxy@0.7.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @finastra/nestjs-proxy
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2022-31069, inspect your project dependencies using npm:
npm ls @finastra/nestjs-proxy
Analyze the terminal output to locate any version of @finastra/nestjs proxy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.7.0), your application is affected.
Note: The npm ls @finastra/nestjs-proxy command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In @finastra/nestjs proxy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-31069 Affected @finastra/nestjs proxy Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@finastra/nestjs-proxy
|
npm |
< 0.7.0
|
0.7.0
|
References
Frequently Asked Questions
What is CVE-2022-31069?
Which @finastra/nestjs proxy versions are affected?
What version fixes CVE-2022-31069?
Is @finastra/nestjs-proxy affected?
What is the CVSS score of CVE-2022-31069?
What CWE is associated with CVE-2022-31069?
How can I check npm dependencies for CVE-2022-31069?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-j562-c3cw-3p5g",
"modified" : "2022-06-17T21:39:48Z",
"published" : "2022-06-17T21:39:48Z",
"aliases" : [ "CVE-2022-31069" ],
"summary" : "Potential Authorization Header Exposure in NPM Packages @finastra/nestjs-proxy, @ffdc/nestjs-proxy",
"details" : "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.\n\nA 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.\n\n### Patches\n- This issue has been fixed in version 0.7.0 of `@finastra/nestjs-proxy`.\n- 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.\n\n### References\n- https://github.com/Finastra/finastra-nodejs-libs/pull/231\n- https://github.com/Finastra/finastra-nodejs-libs/blob/master/libs/proxy/README.md",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@finastra/nestjs-proxy"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.7.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/Finastra/finastra-nodejs-libs/security/advisories/GHSA-j562-c3cw-3p5g"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-31069"
}, {
"type" : "WEB",
"url" : "https://github.com/Finastra/finastra-nodejs-libs/pull/231"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/Finastra/finastra-nodejs-libs"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2022-06-17T21:39:48Z",
"nvd_published_at" : "2022-06-15T19:15:00Z"
}
}