Is CVE-2021-23664 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2021-23664 being exploited in the wild.

How severe is CVE-2021-23664?

Low severity, with a CVSS score of 3.1, published 26 January 2022.

Which products and versions are affected?

@isomorphic-git/cors-proxy (npm) SEMVER:introduced=0,fixed=2.7.1.

Is there a fix for CVE-2021-23664?

Yes. @isomorphic-git/cors-proxy (npm): upgrade to 2.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2021-23664 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2021-23664?

Check whether you run @isomorphic-git/cors-proxy (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2021-23664: @isomorphic-git/cors-proxy server-side request forgery

CVE-2021-23664 · Severity: low · CVSS 3.1 · Published 2022-01-26

@isomorphic-git/cors-proxy is a utility that enables web applications to fetch resources from different origins. A server-side request forgery (SSRF) vulnerability allows attackers to make the proxy server fetch arbitrary URLs without authorization, potentially exposing internal services, stealing credentials, or accessing metadata endpoints on cloud infrastructure.

Vendors: npm.

Quick answers

Is CVE-2021-23664 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2021-23664 being exploited in the wild.
How severe is CVE-2021-23664?: Low severity, with a CVSS score of 3.1, published 26 January 2022.
Which products and versions are affected?: @isomorphic-git/cors-proxy (npm) SEMVER:introduced=0,fixed=2.7.1.
Is there a fix for CVE-2021-23664?: Yes. @isomorphic-git/cors-proxy (npm): upgrade to 2.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2021-23664 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2021-23664?: Check whether you run @isomorphic-git/cors-proxy (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@isomorphic-git/cors-proxy (npm): upgrade to 2.7.1 or later
```
npm install @isomorphic-git/cors-proxy@2.7.1
```

Technical details

The vulnerability is a Server-Side Request Forgery (SSRF) in @isomorphic-git/cors-proxy before version 2.7.1, caused by missing sanitization and validation of the redirection action in the middleware.js component. The proxy follows HTTP redirects without proper validation, allowing an attacker to supply a malicious URL that the server will follow, reaching internal or restricted network resources. The attack requires only network access to the proxy server and no authentication. An attacker can leverage this to scan internal networks, access cloud metadata services, or reach services only accessible from the proxy's network. The vulnerability was patched in version 2.7.1 by disabling automatic redirect following.

Affected products

isomorphic-git @isomorphic-git/cors-proxy before 2.7.1

Identifiers

CVE-2021-23664
GHSA-v82v-rq72-phq9

Timeline

2022-01-26: disclosed
2022-01-24: patched: Fix released in version 2.7.1

References

https://github.com/isomorphic-git/cors-proxy/commit/1b1c91e71d946544d97ccc7cf0ac62b859e03311

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.