# CVE-2018-1216: Hardcoded credentials in vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement)

> A hard-coded password in Dell EMC vApp Manager allows remote attackers to gain unauthorized access to the system via web servlets.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xp9f-vm29-4q5v

## What is CVE-2018-1216?

CVE-2018-1216 is a critical vulnerability in vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement), published on 8 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A hard-coded password vulnerability was discovered in vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement): Dell EMC Unisphere for VMAX Virtual Appliance versions prior to 8.4.0.18, Dell EMC Solutions Enabler Virtual Appliance versions prior to 8.4.0.21, Dell EMC VASA Virtual Appliance versions prior to 8.4.0.514, and Dell EMC VMAX Embedded Management (eManagement) versions prior to and including 1.4 (Enginuity Release 5977.1125.1125 and earlier). They contain an undocumented default account (smc) with a hard-coded password that may be used with certain web servlets. A remote attacker with the knowledge of the hard-coded password and the message format may use vulnerable servlets to gain unauthorized access to the system. Note: This account cannot be used to log in via the web user interface.

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

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

It affects 4 products.


Products: Dell Emc Solutions Enabler Virtual Appliance, Dell Emc Unisphere for Vmax Virtual Appliance, Dell Emc Vasa Virtual Appliance, Dell Emc Vmax Embedded Management.

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

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

## Is CVE-2018-1216 being exploited?

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

## Other vulnerabilities in vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement)

- [CVE-2018-1215](https://insights.sbomify.com/CVE-2018-1215/): File upload in vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement) (high 8.8)
- [CVE-2022-45103](https://insights.sbomify.com/CVE-2022-45103/): Information disclosure in Unisphere for PowerMax vApp (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1216 is a critical vulnerability in vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement), published on 8 Mar 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-1216 in the wild and no public exploit code.

Affected product: vApp Manager which is embedded in Dell EMC Unisphere for VMAX, Dell EMC Solutions Enabler, Dell EMC VASA Virtual Appliances, and Dell EMC VMAX Embedded Management (eManagement). 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-1216/ (Markdown: https://insights.sbomify.com/CVE-2018-1216/index.md)
```

## Sources

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

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