dbcve.org
Integrated Management Module 2Plugin / extension · Lenovo

CVE-2017-3774

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-19
Fix available
A fix is available. Upgrade to 4.70 / 6.60 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack overflow vulnerability in the web administration service (IMM2) allows remote attackers to send specially crafted user ID and password credentials that overflow a stack-based buffer during the authentication routine, causing stack corruption and potentially enabling remote code execution.

MitigationUpdate IMM2 firmware to version 4.70 or later for Lenovo servers, or version 6.60 or later for IBM servers. Apply the appropriate firmware patch from the vendor as soon as possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Integrated Management Module 2Plugin / extension
Affected:< 4.70< 6.60

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the target system uses IMM2
    Determine if the server is a Lenovo or IBM system that includes the Integrated Management Module 2 (IMM2) for remote management. This is typically found on ThinkServer, System x, and BladeCenter servers.
    Affected if The system does not have IMM2, then this CVE does not apply.
  2. Check IMM2 firmware version
    Access the IMM2 web interface or use IPMI commands to retrieve the firmware version. In the web UI, this is usually found under 'IMM Settings' or 'System Information'. Via IPMI, use 'ipmitool raw' or check the BMC firmware version which includes IMM2.
    Affected if The installed version is below 4.70 for Lenovo IMM2, or below 6.60 for IBM IMM2.
  3. Verify web administration service is enabled
    Check if the IMM2 web interface is accessible and enabled. Log into the IMM2 web UI or verify via IPMI that the web service (HTTP/HTTPS) is active on the standard IMM ports (80/443 or 8080/8443).
    Affected if The web administration service is disabled, the attack surface is reduced though the vulnerable code may still be present.
  4. Confirm authentication interface is exposed
    Attempt to access the IMM2 login page via browser or verify the '/api/login' or similar authentication endpoint is reachable. The vulnerability triggers during the user ID/password authentication routine.
    Affected if The IMM2 web login page is publicly or internally accessible on the network, making the authentication routine reachable.

If the system has IMM2 with firmware below 4.70 (Lenovo) or below 6.60 (IBM) AND the web administration service is accessible, the environment is likely affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.70 / 6.60 or later
Fixed in 4.706.60
Interim mitigation

Update IMM2 firmware to version 4.70 or later for Lenovo servers, or version 6.60 or later for IBM servers. Apply the appropriate firmware patch from the vendor as soon as possible.

Recommended fix High confidence

IMM2 firmware 4.70 (Lenovo servers) or 6.60 (IBM servers)

  1. 1. Identify the server model and determine if it uses Lenovo IMM2 or IBM IMM2 firmware
  2. 2. Access the Lenovo support site (support.lenovo.com) or IBM support to download the appropriate IMM2 firmware update
  3. 3. For Lenovo servers: download IMM2 firmware version 4.70 or later
  4. 4. For IBM servers: download IMM2 firmware version 6.60 or later
  5. 5. Upload the firmware update through the IMM2 web interface or via IPMI/Redfish API
  6. 6. Verify the firmware version after update matches the target fixed version
Caveat Firmware updates carry risk of BMC outage; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integrated Management Module 2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3774 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-3774 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data