An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: GSA_kwCzR0hTQS13bTYzLTc2MjctY2gzM84AA3P1
@vendure/core's insecure currencyCode handling allows wrong payment amounts
Currently, in many Vendure deployments it's possible to select any currencyCode (really any, doesn't need to be assigned to the channel) and pay through Mollie and Stripe in that particular currencyCode. The prices are not transformed. The result is the Order is in Payment Settled in the foreign currency. See SS, CZK is not in the channel. I've tested with Mollie and Stripe it both works.
After looking into this further and with help from the comments below, the root cause of this vulnerability is the ability to specify an arbitrary
currencyCode as a query parameter to an API call, and then Vendure will use this and pass it to the rest of the system as
The solution is to add validation to the passed
currencyCode to ensure that it matches one of the available
availableCurrencyCodes of the active Channel.
Furthermore, an additional check has been added for when the currencyCode changes during the AddingItems stage - in this case we need to re-calculate the prices in the new currency.
You can define a custom OrderProcess onTransitionStart function which can verify the order's
currencyCode is as expected before allowing the transition to the
Source: GitHub Advisory Database
Published: 11 days ago
Updated: 11 days ago
CVSS Score: 5.3
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Fixed in: 2.1.3