# CVE-2018-14735: Information disclosure in n/a

> A remote attacker can exploit a messaging permission flaw in Hitachi Command Suite to expose sensitive information via crafted messages.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g76q-f38j-rpvf

## What is CVE-2018-14735?

CVE-2018-14735 is a high-severity vulnerability in n/a, published on 9 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Information Exposure issue was discovered in Hitachi Command Suite 8.5.3. A remote attacker may be able to exploit a flaw in the permission of messaging that may allow for information exposure via a crafted message.

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

## Which versions are affected by CVE-2018-14735?

It affects 6 products.


Products: Hitachi Command Suite, Hitachi Compute Systems Manager, Hitachi Device Manager, Hitachi Replication Manager, Hitachi Tiered Storage Manager, Hitachi Tuning Manager.

## How do I fix CVE-2018-14735?

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

## Is CVE-2018-14735 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14735 and fix it if it is affected.

What it is: CVE-2018-14735 is a high-severity vulnerability in n/a, published on 9 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-14735 in the wild and no public exploit code.

Affected product: n/a. 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-2018-14735/ (Markdown: https://insights.sbomify.com/CVE-2018-14735/index.md)
```

## Sources

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

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