# CVE-2022-42443: Trusteer for mobile file upload

> An issue in Trusteer mobile SDKs allows unauthorized file uploads, potentially leading to code execution or data modification.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2024
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rxj9-qx32-5mw6

## What is CVE-2022-42443?

CVE-2022-42443 is a low-severity vulnerability in IBM Trusteer Android SDK, published on 17 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2022-42443?

It affects 2 products.


Products: Ibm Trusteer Android Sdk for Mobile, Ibm Trusteer Ios Sdk for Mobile.

## How do I fix CVE-2022-42443?

No fix has been published for CVE-2022-42443 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-42443 being exploited?

There is no known exploitation of CVE-2022-42443 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42443 and fix it if it is affected.

What it is: CVE-2022-42443 is a low-severity vulnerability in IBM Trusteer Android SDK, published on 17 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-42443 in the wild and no public exploit code.

Affected product: IBM Trusteer Android SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-42443/ (Markdown: https://insights.sbomify.com/CVE-2022-42443/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-42443
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-42443
- OSV: https://osv.dev/vulnerability/CVE-2022-42443

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-42443/
Summaries are generated and may contain mistakes; the official description above is the record.