Latest / Decrypted: The UK Cyber Briefing / A Magento zero-day is backdooring stores while Adobe still has no patch
Transcript
- 0:03This is Decrypted. Sunday, the sixth of September.
- 0:06A Magento zero-day is backdooring stores while Adobe still has no patch.
- 0:12A zero-day in Magento and Adobe Commerce is backdooring online stores right now, and there is no patch, no C
- 0:20V E and, as of this morning, no confirmed date for either.
- 0:25Dutch security firm Sansec, which caught the first attacks at 22:20 U T C on 4 September, has dubbed it Style
- 0:34Smuggler. It works against every current version of the platform, including 2.
- 0:394.9, and it has already compromised at least one store running 2.
- 0:434.6-p15 with July and August's security updates fully applied.
- 0:49For the many UK retailers who still run Magento or Adobe Commerce behind their checkout, patch status is not
- 0:56what stands between them and this attack.
- 0:58Next. How it works.
- 1:07her or not they use it. An attacker sends a crafted request that manipulates a "styles" property, smuggling P
- 1:14H P code into a file Magento itself generates during normal operation, such as a failure report.
- 1:20Nothing runs yet: the code just sits there, planted.
- 1:24The second stage is the clever part.
- 1:27Magento's own automated "Payment Transaction Failed" email, the one that fires whenever a card gets declined,
- 1:35reads and executes that planted file as it builds the message.
- 1:39The store's own housekeeping does the attacker's work for it.
- 1:43No login, no password, no privileged account: just two ordinary-looking requests to features the store was al
- 1:51ready running.
- 1:55Sansec's own test stores prove the point: current builds, current patch levels, no exposure to any previousl
- 2:03y known bug, still fell. That is the definition of a zero-day, but it is worth dwelling on because so much of
- 2:10retail security is built around "are we patched.
- 2:13" Here, being patched against every known C V E left a store just as open as one running years-old code, becau
- 2:21se the vulnerable behaviour was never a known bug to begin with.
- 2:24Adobe's next scheduled security release lands on 8 September; whether it covers this flaw is not yet confirme
- 2:31d.
- 2:34The design failure here is a feature left on by default that most stores never asked for.
- 2:40GraphQL ships enabled even on storefronts running a traditional theme rather than a headless or app frontend,
- 2:48so it sits exposed with no business justification.
- 2:50Secure by Design, in the N C S C's own language, means shipping products where the safe configuration is the
- 2:58default one, not an opt-in a store owner has to discover after the fact.
- 3:03For any UK organisation running Magento or Adobe Commerce, the immediate move is to disable GraphQL unless a
- 3:11headless frontend genuinely needs it, and to treat "we're on the latest patch" as necessary but no longer suff
- 3:18icient. Store owners should also watch for unexplained "kworker" processes or a burst of Payment Transaction F
- 3:25ailed emails, both signs Sansec flags as compromise indicators.
- 3:30That was Decrypted. The written version and every source are linked in the show notes.
- 3:35Thanks for listening.