Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 17 November 2023.

Which products and versions are affected?

@vendure/core (npm) SEMVER:introduced=0,fixed=2.1.3.

Is there a fix for This vulnerability?

Yes. @vendure/core (npm): upgrade to 2.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

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

Check whether you run @vendure/core (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.

Vendure insecure currencyCode handling in payment processing

Severity: low · CVSS 3.1 · Published 2023-11-17

Vendure, a popular headless e-commerce platform, failed to validate which currencies customers could use during checkout. Attackers could select any currency code—not just those supported by the merchant—and complete payment transactions at incorrect amounts, resulting in customers paying vastly different amounts than expected or merchants receiving payments in unsupported currencies.

Technologies: @vendure/core (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 17 November 2023.
Which products and versions are affected?: @vendure/core (npm) SEMVER:introduced=0,fixed=2.1.3.
Is there a fix for This vulnerability?: Yes. @vendure/core (npm): upgrade to 2.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run @vendure/core (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

@vendure/core (npm): upgrade to 2.1.3 or later
```
npm install @vendure/core@2.1.3
```

Technical details

The vulnerability stems from insufficient validation of the currencyCode query parameter passed to Vendure API calls. The application accepted and propagated arbitrary currency codes through RequestContext.currencyCode without verifying they matched the channel's availableCurrencyCodes. An unauthenticated network attacker could specify any currency code during the checkout flow, and Vendure would pass it to payment gateways (Mollie, Stripe) without transformation or validation, allowing payment in unintended currencies. The fix (v2.1.3) adds validation to ensure currencyCode matches the active channel's supported currencies and re-calculates prices if the currency changes during the AddingItems stage.

Affected products

Vendure core < 2.1.3

Timeline

2023-11-17: disclosed
2023-11-17: patched: v2.1.3 released

References

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