M2: Inadequate Mobile Supply Chain Security

M2: Inadequate Mobile Supply Chain Security

An SDK update the team never chose shipped inside their app.

What Is M2: Inadequate Mobile Supply Chain Security?

A mobile app that accepts any new version of a third-party SDK ships whatever that vendor's account publishes next. You'll watch an attacker push a malicious SDK release that harvests contacts through apps that never chose to upgrade, then contain it, pin the dependency and verify its checksums.

What You'll Learn in M2: Inadequate Mobile Supply Chain Security

M2: Inadequate Mobile Supply Chain Security — Training Steps

  1. A release he did not write

    Statlume makes a small analytics SDK that hundreds of shopping and delivery apps build into their Android, iOS and React Native code. Two days ago Bob phished the password of the Statlume engineer who publishes it, and used that account to push a new version, 4.2.0, to all three package registries. It looks like a routine minor update. It also quietly adds a contact sync that sends each user's address book to Bob.

  2. Count who pulled it

    Bob still holds the vendor's registry token, so he can read the same download statistics Statlume's own team sees.

  3. Read the collector

    The contact sync posts to a collector Bob runs. He checks what it has received since the release went out.

  4. How the update arrived

  5. A message from Tomasz

    Before the details land in her inbox, Tomasz Wierzba messages Alice directly.

  6. Customers are confused

    Alice leads the mobile team at Pantrova. Version 7.3.1 of the app reached customers yesterday. The support lead has written to her.

  7. Open the app

    Alice's test phone has the store build of 7.3.1. She wants to see the prompt for herself.

  8. A request nobody wrote

    Before the home screen even settles, Android asks whether Pantrova may access her contacts. A grocery app has no reason to read her address book, and her team never added this.

  9. What changed in the build

    Nobody on the team touched the build files for 7.3.1. Alice compares the lockfiles, which record the exact version of every library each release was built with.

  10. Ask the vendor

    A minor version that asks for contacts is not something a careful vendor ships quietly. Alice checks whether Statlume knows about 4.2.0.

Security Framework Coverage

OWASP Mobile Top 10

  • M2:2024 Inadequate Supply Chain Security

OWASP MASVS

  • MASVS-CODE-3 The app only uses software components without known vulnerabilities.

CWE

  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere
  • CWE-359 Exposure of Private Personal Information to an Unauthorized Actor

MITRE ATT&CK

  • T1474.003 Supply Chain Compromise: Compromise Software Supply Chain

CIS Controls

  • CIS 16 Application Software Security

NIST CSF

  • PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
  • PR.PS Platform Security

NICE Framework

  • DD-WRL-003 Secure Software Development
  • OG-WRL-017 Cybersecurity Supply Chain Risk Management