# CVE-2024-35118: IBM MaaS360 information disclosure

> Attackers with physical access to the device can extract hardcoded credentials from the IBM MaaS360 Android application, leading to information disclosure.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 29 Aug 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-2c63-x392-hx7w

## What is CVE-2024-35118?

CVE-2024-35118 is a medium-severity vulnerability in IBM MaaS360, published on 29 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM MaaS360 for Android 6.31 through 8.60 is using hard coded credentials that can be obtained by a user with physical access to the device.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2024-35118?

It affects 1 product.


Products: Ibm Maas360 Mdm.

## How do I fix CVE-2024-35118?

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

## Is CVE-2024-35118 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35118 and fix it if it is affected.

What it is: CVE-2024-35118 is a medium-severity vulnerability in IBM MaaS360, published on 29 Aug 2024. 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-2024-35118 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-2024-35118/ (Markdown: https://insights.sbomify.com/CVE-2024-35118/index.md)
```

## Sources

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

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