Safeguard
Vulnerability Analysis•

CVE-2022-42443: Low File Upload Issue in IBM Trusteer SDK

CVE-2022-42443 is a low (2.2) file upload issue in IBM Trusteer SDKs before 5.7 for iOS and Android. Rebuild your apps with SDK 5.7 or later.

Safeguard Security Team
4 min read

CVE-2022-42443 is a low severity (CVSS 2.2) issue in the IBM Trusteer SDK for iOS and Android, all versions before 5.7. IBM describes an undisclosed issue that may allow uploading of files. The fix is to rebuild and redeploy your mobile apps with Trusteer SDK 5.7 or later.

What's affected

IBM's bulletin lists Trusteer iOS SDK for mobile and Trusteer Android SDK for mobile, all versions prior to 5.7, as affected. The fixed version for both is 5.7 or later. The bulletin describes an undisclosed issue in Trusteer agents that may allow uploading of files.

The record scores it 2.2 (Low) with vector CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N: network reachable but with high attack complexity, high privileges required and only a low integrity impact. IBM's CVSS 3.0 vector in the bulletin is the same. The class is CWE-434 (Unrestricted Upload of File with Dangerous Type).

An SDK is different from a server product. The affected code is compiled into your own mobile app, so the vulnerable version is whatever you last built, not what is running in a data center.

How to check if you're exposed

Look in your mobile projects for the Trusteer SDK and its version. The place to look depends on how the SDK was added. For many vendor SDKs it is a framework or library file added to the project by hand, so search your repositories and your build configuration:

grep -ril trusteer .

Then check the SDK version recorded in your build files or in the release notes you received from IBM, and compare it with 5.7. Remember that app store builds already in users' hands keep the SDK version they were built with. Check which app versions are still in circulation.

What to do now

  1. Find every iOS and Android app that embeds the Trusteer SDK.
  2. Download Trusteer Mobile SDK 5.7 or later from IBM's customer portal, as the bulletin directs.
  3. Rebuild the apps with the new SDK. IBM says no code changes are needed to take advantage of the improvements, but the apps must be rebuilt and redeployed.
  4. Publish the new builds and plan how long you will support older app versions.
  5. Record the SDK version in your software bill of materials so a future advisory is a lookup.

Why it matters

The score is low and the bulletin is brief, so this is not an emergency. It is still a good example of an SDK problem: the fix reaches users only after you rebuild, ship and have them update. Until then, old app versions carry the old code.

The vector tells you why the score is low. An attacker would need elevated privileges and favorable conditions, and the effect is a minor integrity impact. IBM describes the issue only as undisclosed, so there is little more to say about the mechanism, and I will not speculate. The record's KEV flag is false, and the bulletin does not report exploitation.

Quick check

Do I need to change my code?

IBM says no code changes are required, but you must rebuild with the new SDK and redeploy your apps.

Why does the score look so low?

The vector requires high privileges and high attack complexity, with only a low integrity impact.

Sources

Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.