# CVE-2017-3774: Memory corruption in IMM2

> An attacker can cause stack corruption in the IMM2 web administration service via crafted credentials, potentially leading to code execution or denial of service.

- **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:** 19 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4qmr-v28r-p74f

## What is CVE-2017-3774?

CVE-2017-3774 is a critical memory corruption vulnerability in IBM IMM2, published on 19 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack overflow vulnerability was discovered within the web administration service in Integrated Management Module 2 (IMM2) earlier than version 4.70 used in some Lenovo servers and earlier than version 6.60 used in some IBM servers. An attacker providing a crafted user ID and password combination can cause a portion of the authentication routine to overflow its stack, resulting in stack corruption.

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

## Which versions are affected by CVE-2017-3774?

It affects 1 product.


Products: Lenovo Integrated Management Module 2.

## How do I fix CVE-2017-3774?

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

## Is CVE-2017-3774 being exploited?

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

## Other vulnerabilities in IBM IMM2

- [CVE-2020-8340](https://insights.sbomify.com/CVE-2020-8340/): Cross-site scripting in System x IMM2 firmware (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3774 and fix it if it is affected.

What it is: CVE-2017-3774 is a critical memory corruption vulnerability in IBM IMM2, published on 19 Apr 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-2017-3774 in the wild and no public exploit code.

Affected product: IBM IMM2. 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-2017-3774/ (Markdown: https://insights.sbomify.com/CVE-2017-3774/index.md)
```

## Sources

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

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