CVE-2017-3744
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 · uneditedIn the IMM2 firmware of Lenovo System x servers, remote commands issued by LXCA or other utilities may be captured in the First Failure Data Capture (FFDC) service log if the service log is generated when that remote command is running. Captured command data may contain clear text login information. Authorized users that can capture and export FFDC service log data may have access to these remote commands.
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 confidenceThe IMM2 firmware in Lenovo System x servers has an information disclosure vulnerability where remote commands executed via LXCA or other utilities are captured in the First Failure Data Capture (FFDC) service log when that log is generated during command execution. This log can include cleartext login credentials, allowing authorized users with FFDC log access to obtain sensitive authentication information.
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<= 4.9<= 6.19CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify IMM firmware versionAccess the Integrated Management Module web interface or use ipmitool: 'ipmitool -I lanplus -H <IMM_IP> -U <user> -P <pass> raw' or check via LXCA utility under Hardware -> System x -> IMM -> Firmware VersionAffected if The firmware version is Lenovo IMM2 <= 4.9 or IBM IMM <= 6.19
-
Verify FFDC log generation is enabledCheck IMM configuration settings for First Failure Data Capture service - typically found in IMM web UI under Service Settings or through ipmitool: 'ipmitool -I lanplus -H <IMM_IP> -U <user> -P <pass> raw 0x32 0x76 0x01'Affected if FFDC service is enabled and configured to capture command execution logs
-
Locate FFDC service logsAccess FFDC logs via LXCA (Hardware -> System x -> IMM -> Service and Diagnostics -> FFDC Logs) or via IMM web interface if available, or download via ipmitoolAffected if FFDC logs exist and are accessible to authorized users
-
Inspect FFDC logs for credentialsOpen any FFDC logs generated during remote command execution (via LXCA or ipmitool) and search for cleartext user credentials, passwords, or authentication tokens in the log contentAffected if FFDC logs contain cleartext login credentials or sensitive authentication information
A system is affected if the IMM firmware version is at or below 4.9 (Lenovo) or 6.19 (IBM), FFDC logging is enabled, and FFDC logs are accessible to users who should not see credentials.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate IMM2 firmware to a patched version and restrict access to FFDC service logs; rotate any credentials that may have been exposed in existing logs.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3744 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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