# CVE-2017-1422: Information disclosure in MaaS360 DTM

> An attacker can access sensitive information due to improper verification of user rights in IBM MaaS360 DTM applications.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7wp4-4p7f-66cr

## What is CVE-2017-1422?

CVE-2017-1422 is a low-severity vulnerability in IBM MaaS360 DTM, published on 22 Aug 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM MaaS360 DTM all versions up to 3.81 does not perform proper verification for user rights of certain applications which could disclose sensitive information. IBM X-Force ID: 127412.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-1422?

It affects 1 product.


Products: Ibm Maas360 Dtm.

## How do I fix CVE-2017-1422?

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

## Is CVE-2017-1422 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1422 and fix it if it is affected.

What it is: CVE-2017-1422 is a low-severity vulnerability in IBM MaaS360 DTM, published on 22 Aug 2017. 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-2017-1422 in the wild and no public exploit code.

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

## Sources

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

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