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

> Authenticated remote users can expose technical information via error messages in Hitachi Command Suite and Automation Director.

- **Severity:** Medium 4.3 (`CVSS:3.0/AC:L/AV:N/A:N/C:L/I:N/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7r29-2mx5-wh83

## What is CVE-2018-21032?

CVE-2018-21032 is a medium-severity vulnerability in n/a, published on 14 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in Hitachi Command Suite prior to 8.7.1-00 and Hitachi Automation Director prior to 8.5.0-00 allow authenticated remote users to expose technical information through error messages. Hitachi Command Suite includes Hitachi Device Manager and Hitachi Compute Systems Manager.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 3 products.


Products: Hitachi Automation Director, Hitachi Compute Systems Manager, Hitachi Device Manager.

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

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

## Is CVE-2018-21032 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36652](https://insights.sbomify.com/CVE-2020-36652/): Misconfiguration in Hitachi Automation Director (medium 6.6)
- [CVE-2018-21033](https://insights.sbomify.com/CVE-2018-21033/): Cross-site scripting in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-21032 is a medium-severity vulnerability in n/a, published on 14 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21032 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-21032/ (Markdown: https://insights.sbomify.com/CVE-2018-21032/index.md)
```

## Sources

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

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