CVE-2018-9071
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 · uneditedLenovo Chassis Management Module (CMM) prior to version 2.0.0 allows unauthenticated users to retrieve information related to the current authentication configuration settings. Exposed settings relate to password lengths, expiration, and lockout configuration.
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 confidenceLenovo Chassis Management Module (CMM) versions prior to 2.0.0 contain an information disclosure vulnerability where unauthenticated users can retrieve authentication configuration settings including password length requirements, expiration policies, and account lockout thresholds. This is a pre-authentication information leak that could aid attackers in planning credential-based attacks.
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< 2.0.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm Lenovo CMM is accessible on the networkAttempt to reach the Lenovo Chassis Management Module web interface via HTTP/HTTPS on the management IP address (common ports 80, 443, or vendor-defined management ports). Look for Lenovo branding or CMM-specific login pages.Affected if The CMM web interface responds and is reachable over the network.
-
Identify the installed CMM firmware versionLocate the firmware version displayed on the CMM login page, in the system information section, or via SNMP/OOB management interfaces. Common locations include the login page footer, 'About' or 'System Info' pages, or the SNMP sysDescr OID.Affected if A firmware version string is displayed (for example, 1.x.x or 2.0.0).
-
Compare version against the affected rangeCompare the identified firmware version to the vulnerable range. Versions prior to 2.0.0 are affected (for example, 1.8.5, 1.9.2, etc.).Affected if The installed version is less than 2.0.0 (for example, 1.9.0, 1.5.3, etc.).
-
Verify pre-authentication information leak is presentAttempt to access authentication configuration endpoints without providing credentials. On vulnerable versions, unauthenticated requests to certain paths may return password policy, lockout threshold, or account configuration details.Affected if Authentication configuration details (password length, expiration, lockout thresholds) are returned without requiring login.
Your environment is affected if the Lenovo CMM management interface is network-accessible and the installed firmware version is below 2.0.0.
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 data2.0.0
Upgrade Lenovo CMM to version 2.0.0 or later to remediate this vulnerability. Until then, consider network segmentation to limit exposure of the management interface to untrusted networks.
- 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-2018-9071 — 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-2018-9071 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