Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

CVE-2022-31069

MEDIUM

CVE-2022-31069 is a medium-severity (CVSS 5.8) Information Exposure vulnerability in finastra nestjs-proxy. O3 Security detects and blocks CVE-2022-31069 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

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…

Published
Jun 15, 2022
Updated
Jun 17, 2026
Affected
0 pkgs
Patched
None yet
Exploits
None indexed

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.

Affected Products

2 products · 2 configurations
Application
nestjs-proxyfinastra
< 0.7.0
range
Application
nestjs-proxynestjs-proxy_project
≤ 0.4.0
range

Detection & mitigation playbook

Vendor / appliance
  1. Detect

    Inventory every finastra nestjs-proxy deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

  2. Fix

    Apply the finastra nestjs-proxy security patch or hotfix for CVE-2022-31069 on the affected version, following the vendor advisory for your exact build.

  3. Workarounds

    Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

  4. How O3 protects you

    O3 detects and blocks CVE-2022-31069 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2022-31069. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 bas
O3 Security · Runtime Protection

Is CVE-2022-31069 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2022-31069 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.