# CVE-2018-1205: Dell EMC ScaleIO, versions prior to 2.5, do not properly handle some packet data in the MDM service.


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gpqm-7gpf-39qf

## What is CVE-2018-1205?

CVE-2018-1205 is a high-severity vulnerability in Dell EMC ScaleIO, published on 27 Mar 2018. 

### Official description

Dell EMC ScaleIO, versions prior to 2.5, do not properly handle some packet data in the MDM service. As a result, a remote attacker could potentially send specifically crafted packet data to the MDM service causing it to crash.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dell Emc Scaleio.

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

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

## Is CVE-2018-1205 being exploited?

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

## Other vulnerabilities in Dell EMC ScaleIO

- [CVE-2018-1237](https://insights.sbomify.com/CVE-2018-1237/): Auth bypass in ScaleIO (critical 9.8)
- [CVE-2017-8001](https://insights.sbomify.com/CVE-2017-8001/): Information disclosure in EMC ScaleIO EMC ScaleIO 2.0.1.x (high 8.4)
- [CVE-2018-1238](https://insights.sbomify.com/CVE-2018-1238/): Command injection in ScaleIO (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1205 is a high-severity vulnerability in Dell EMC ScaleIO, published on 27 Mar 2018. 
Exploitation: There is no known exploitation of CVE-2018-1205 in the wild and no public exploit code.

Affected product: Dell EMC ScaleIO. 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-1205/ (Markdown: https://insights.sbomify.com/CVE-2018-1205/index.md)
```

## Sources

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

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