Security readout for executives and security teams
Plain-English summary
Keylime before 6.3.0 may process untrusted ZIP data in agent quote responses, allowing a zip-bomb style denial of service. The main business risk is service disruption, not data theft or data modification, based on the supplied CVSS and description.
Executive priority
Treat this as a moderate availability risk for Keylime deployments. Prioritize remediation where Keylime supports production attestation workflows or service disruption would delay security decisions.
Technical view
The issue is CWE-400 resource exhaustion. A quote response from a Keylime agent can include possibly untrusted ZIP content that may expand excessively and consume resources. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.
Likely exposure
Exposure is likely limited to environments running Keylime before 6.3.0 where quote responses from agents are processed. The bundle does not identify affected operating systems, distributions, deployment modes, or downstream packages.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The documented impact is availability loss through zip bombs, with no stated confidentiality or integrity impact.
Researcher notes
Evidence is narrow but consistent: untrusted ZIP data in agent quote responses can trigger resource exhaustion. The supplied CVSS requires user interaction and local attack vector; do not assume remote exploitation without additional vendor evidence.
Mitigation direction
- Upgrade Keylime to 6.3.0 or later if vendor guidance confirms it as fixed.
- Review the GitHub advisory and linked commit for vendor remediation details.
- Restrict Keylime component access to trusted hosts where operationally feasible.
- Monitor Keylime services for abnormal CPU, memory, disk, or decompression failures.
Validation and detection
- Inventory Keylime deployments and record exact installed versions.
- Confirm whether any instance runs a version before 6.3.0.
- Review logs for quote-processing failures or resource exhaustion events.
- Verify vendor advisory status before closing remediation work.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-23951 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://seclists.org/oss-sec/2022/q1/101CVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/security/advisories/GHSA-6xx7-m45w-76m2CVE reference · x_refsource_MISC
- https://github.com/keylime/keylime/commit/6e44758b64b0ee13564fc46e807f4ba98091c355CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.