CVE-2018-9073
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 utilizes a hardcoded encryption key to protect certain secrets. Possession of the key can allow an attacker that has already compromised the server to decrypt these secrets.
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 a hardcoded encryption key used to protect certain sensitive secrets stored on the system. An attacker who has already achieved code execution or server compromise can recover this hardcoded key and decrypt the protected secrets, potentially exposing credentials or other confidential data.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/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.
-
Check Lenovo CMM firmware version via web interfaceLog into the Chassis Management Module web interface and navigate to the firmware information or system status page to view the installed firmware versionAffected if The displayed firmware version is below 2.0.0 (for example, 1.x.x or any version number less than 2.0.0)
-
Check Lenovo CMM firmware version via CLIAccess the CMM command-line interface via SSH or serial console and run the appropriate command to display firmware version information, such as 'show firmware' or 'version'Affected if The reported firmware version is prior to 2.0.0
-
Identify CMM model and confirm it is a Lenovo productLocate the physical chassis or documentation that identifies the Lenovo Chassis Management Module model and confirm it uses the affected firmwareAffected if The device is a Lenovo CMM running firmware versions before 2.0.0
-
Check for evidence of prior compromiseReview system logs, audit trails, or security monitoring alerts for signs of unauthorized code execution or server compromise that could have enabled an attacker to recover the hardcoded keyAffected if Evidence exists of prior unauthorized access or code execution on the CMM system
A system is affected if it runs Lenovo Chassis Management Module firmware version 1.x.x or any version lower than 2.0.0, especially if there is any indication that an attacker may have already gained code execution on that system.
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 Chassis Management Module to version 2.0.0 or later to remove the hardcoded encryption key. If upgrading is not immediately possible, restrict physical and network access to the CMM management interface to reduce the attack surface.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9073 — 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-9073 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