# CVE-2018-9073: CMM Security Vulnerability


- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 16 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9jw6-h58q-m3jf

## What is CVE-2018-9073?

CVE-2018-9073 is a medium-severity vulnerability in Lenovo Chassis Management Module (CMM), published on 16 Nov 2018. 

### Official description

Lenovo 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2018-9073?

It affects 1 product.


Products: Lenovo Chassis Management Module Firmware.

## How do I fix CVE-2018-9073?

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

## Is CVE-2018-9073 being exploited?

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

## Other vulnerabilities in Lenovo Chassis Management Module (CMM)

- [CVE-2018-9071](https://insights.sbomify.com/CVE-2018-9071/): CMM Security Vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9073 and fix it if it is affected.

What it is: CVE-2018-9073 is a medium-severity vulnerability in Lenovo Chassis Management Module (CMM), published on 16 Nov 2018. 
Exploitation: There is no known exploitation of CVE-2018-9073 in the wild and no public exploit code.

Affected product: Lenovo Chassis Management Module (CMM). 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-2018-9073/ (Markdown: https://insights.sbomify.com/CVE-2018-9073/index.md)
```

## Sources

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

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