# CVE-2019-4735: Information disclosure in MaaS360

> An attacker with physical access to an iOS device can extract sensitive data from the IBM MaaS360 agent outside its secure container.

- **Severity:** Low 2.4 (`CVSS:3.0/PR:N/AC:L/AV:P/S:U/C:L/A:N/I:N/UI:N/RC:C/RL:O/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w2cq-62g9-8425

## What is CVE-2019-4735?

CVE-2019-4735 is a low-severity vulnerability in IBM MaaS360, published on 23 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM MaaS360 3.96.62 for iOS could allow an attacker with physical access to the device to obtain sensitive information from the agent outside of the container. IBM X-Force ID: 172705.

## Which versions are affected by CVE-2019-4735?

It affects 1 product.


Products: Ibm Maas360.

## How do I fix CVE-2019-4735?

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

## Is CVE-2019-4735 being exploited?

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

## Other vulnerabilities in IBM MaaS360

- [CVE-2020-4353](https://insights.sbomify.com/CVE-2020-4353/): Denial of service in MaaS360 (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4735 and fix it if it is affected.

What it is: CVE-2019-4735 is a low-severity vulnerability in IBM MaaS360, published on 23 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4735 in the wild and no public exploit code.

Affected product: IBM MaaS360. 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-2019-4735/ (Markdown: https://insights.sbomify.com/CVE-2019-4735/index.md)
```

## Sources

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

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