# CVE-2018-1206: Hardcoded credentials in Dell EMC Data Protection Advisor versions prior to 6.3 Patch 159 and Dell EMC Data Protection Advisor versions prior to 6.4 Patch 110

> An attacker with local access can use hardcoded administrative credentials to gain unauthorized access to the Data Protection Advisor database.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 12 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7c88-c2gq-h35v

## What is CVE-2018-1206?

CVE-2018-1206 is a high-severity vulnerability in Dell EMC Data Protection Advisor versions prior to 6.3 Patch 159 and Dell EMC Data Protection Advisor versions prior to 6.4 Patch 110, published on 12 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dell EMC Data Protection Advisor versions prior to 6.3 Patch 159 and Dell EMC Data Protection Advisor versions prior to 6.4 Patch 110 contain a hardcoded database account with administrative privileges. The affected account is "apollosuperuser." An attacker with local access to the server where DPA Datastore Service is installed and knowledge of the password may potentially gain unauthorized access to the database. Note: The Datastore Service database cannot be accessed remotely using this account.

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

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

It affects 1 product.


Products: Emc Data Protection Advisor.

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

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

## Is CVE-2018-1206 being exploited?

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

## Other vulnerabilities in Dell EMC Data Protection Advisor versions prior to 6.3 Patch 159 and Dell EMC Data Protection Advisor versions prior to 6.4 Patch 110

- [CVE-2017-8013](https://insights.sbomify.com/CVE-2017-8013/): Hardcoded credentials in EMC Data Protection Advisor (critical 9.8)
- [CVE-2017-10955](https://insights.sbomify.com/CVE-2017-10955/): Command injection in Dell EMC Data Protection Advisor (high 8.8)
- [CVE-2017-8002](https://insights.sbomify.com/CVE-2017-8002/): SQL injection in EMC Data Protection Advisor prior to 6.4 (high 8.8)
- [CVE-2012-0406](https://insights.sbomify.com/CVE-2012-0406/): Null dereference in n/a (high 7.8)
- [CVE-2012-4616](https://insights.sbomify.com/CVE-2012-4616/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1206 is a high-severity vulnerability in Dell EMC Data Protection Advisor versions prior to 6.3 Patch 159 and Dell EMC Data Protection Advisor versions prior to 6.4 Patch 110, published on 12 Mar 2018. 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-2018-1206 in the wild and no public exploit code.

Affected product: Dell EMC Data Protection Advisor versions prior to 6.3 Patch 159 and Dell EMC Data Protection Advisor versions prior to 6.4 Patch 110. 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-1206/ (Markdown: https://insights.sbomify.com/CVE-2018-1206/index.md)
```

## Sources

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

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