# CVE-2018-1217: Missing authorization in Avamar, Integrated Data Protection Appliance

> Remote unauthenticated attackers can read or modify Local Download Service credentials in Dell EMC Avamar Installation Manager, potentially impersonating service actions.

- **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:** 9 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6583-rv3q-95pf

## What is CVE-2018-1217?

CVE-2018-1217 is a critical missing authorization vulnerability in Dell EMC Avamar, Integrated Data Protection Appliance, published on 9 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Avamar Installation Manager in Dell EMC Avamar Server 7.3.1, 7.4.1, and 7.5.0, and Dell EMC Integrated Data Protection Appliance 2.0 and 2.1, is affected by a missing access control check vulnerability which could potentially allow a remote unauthenticated attacker to read or change the Local Download Service (LDLS) credentials. The LDLS credentials are used to connect to Dell EMC Online Support. If the LDLS configuration was changed to an invalid configuration, then Avamar Installation Manager may not be able to connect to Dell EMC Online Support web site successfully. The remote unauthenticated attacker can also read and use the credentials to login to Dell EMC Online Support, impersonating the AVI service actions using those credentials.

Weakness: CWE-862 (Missing Authorization)

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

It affects 2 products.


Products: Dell Emc Avamar, Dell Emc Integrated Data Protection Appliance.

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

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

## Is CVE-2018-1217 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1217 exists.

Public exploit code:

- Dell EMC Avamar and Integrated Data Protection Appliance Installation Manager - Invalid Access Control (exploitdb)
- Dell EMC Avamar and Integrated Data Protection Appliance Installation Manager - Invalid Access Control (nuclei): http/cves/2018/CVE-2018-1217.yaml

## Other vulnerabilities in Dell EMC Avamar, Integrated Data Protection Appliance

- [CVE-2018-11066](https://insights.sbomify.com/CVE-2018-11066/): Dell EMC Avamar and Integrated Data Protection Appliance Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2018-11077](https://insights.sbomify.com/CVE-2018-11077/): Dell EMC Avamar and Integrated Data Protection Appliance Command Injection Vulnerability (medium 6.7)
- [CVE-2018-11076](https://insights.sbomify.com/CVE-2018-11076/): Dell EMC Avamar and Integrated Data Protection Appliance Information Exposure Vulnerability (medium 6.5)
- [CVE-2018-11067](https://insights.sbomify.com/CVE-2018-11067/): Dell EMC Avamar and Integrated Data Protection Appliance Open Redirection Vulnerability (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1217 is a critical missing authorization vulnerability in Dell EMC Avamar, Integrated Data Protection Appliance, published on 9 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-1217 exists.

Affected product: Dell EMC Avamar, Integrated Data Protection Appliance. 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-1217/ (Markdown: https://insights.sbomify.com/CVE-2018-1217/index.md)
```

## Sources

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

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