dbcve.org
Trusteer Android Sdk For MobileApplication · Ibm

CVE-2022-42443

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-17
Fix available
A fix is available. Upgrade to 5.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An undisclosed issue in Trusteer iOS SDK for mobile versions prior to 5.7 and Trusteer Android SDK for mobile versions prior to 5.7 may allow uploading of files. IBM X-Force ID: 238535.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Trusteer iOS and Android SDK versions prior to 5.7 contain an undisclosed vulnerability that may allow uploading of files. This arbitrary file upload capability, given the CVSS 9.8 rating, likely permits remote code execution or sensitive data exfiltration when exploited.

MitigationUpgrade Trusteer iOS SDK and Trusteer Android SDK to version 5.7 or later in all affected mobile applications. Conduct thorough regression testing post-upgrade to ensure security functionality remains intact.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Trusteer Android Sdk For MobileApplication
Affected:< 5.7
Trusteer Ios Sdk For MobileApplication
Affected:< 5.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Trusteer SDK presence in Android application
    Examine the application's dependency configuration files (such as build.gradle, gradle.lock, or similar) for any Trusteer SDK library references. Alternatively, inspect the compiled APK's lib directory for Trusteer-related native libraries.
    Affected if Trusteer SDK library is found and its version is below 5.7
  2. Identify Trusteer SDK presence in iOS application
    Examine the application's dependency management files (such as Podfile, Cartfile, or Package.swift) for any Trusteer SDK references. Alternatively, inspect the compiled app bundle for Trusteer-related frameworks or libraries.
    Affected if Trusteer SDK framework/library is found and its version is below 5.7
  3. Verify Trusteer SDK version in Android dependencies
    Run a dependency report command (such as ./gradlew app:dependencies or ./gradlew app:dependencies --configuration releaseRuntimeClasspath) and search for Trusteer-related entries. Compare the displayed version against the affected range.
    Affected if The reported Trusteer SDK version is less than 5.7
  4. Verify Trusteer SDK version in iOS dependencies
    For CocoaPods, run pod repo update and pod list to list installed pods and their versions. For Carthage, check the resolved Cartfile.resolved. For Swift Package Manager, check the Package.resolved file. Compare the Trusteer SDK version against the affected range.
    Affected if The reported Trusteer SDK version is less than 5.7

The environment is affected if any installed Trusteer SDK (iOS or Android) is found with a version number less than 5.7.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.7 or later
Fixed in 5.7
Interim mitigation

Upgrade Trusteer iOS SDK and Trusteer Android SDK to version 5.7 or later in all affected mobile applications. Conduct thorough regression testing post-upgrade to ensure security functionality remains intact.

Recommended fix High confidence

5.7

  1. Upgrade Trusteer Android SDK for Mobile to version 5.7 or later
  2. Upgrade Trusteer iOS SDK for Mobile to version 5.7 or later
  3. Verify the upgrade by checking the SDK version in your mobile application
  4. Test that the file upload functionality now properly validates and restricts file types

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Trusteer Android Sdk For Mobile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42443 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data