LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23952: In Keylime before 6.3.0, current keylime installer installs the keylime.conf file, which can contain sensit...

In Keylime before 6.3.0, current keylime installer installs the keylime.conf file, which can contain sensitive data, as world-readable.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Keylime deployments may have installed a configuration file containing sensitive data with permissions that allowed broad reading. The business risk is exposure of secrets stored in keylime.conf, not system takeover by itself. Source data identifies this as high severity due to confidentiality impact.

Executive priority

Treat this as a targeted confidentiality remediation for Keylime systems, not a broad emergency. Prioritize hosts where keylime.conf contains credentials, keys, or service secrets, then rotate exposed values after permissions and versions are corrected.

Technical view

CVE-2022-23952 is a CWE-200 information exposure in Keylime before 6.3.0. The installer created keylime.conf as world-readable even though it can contain sensitive values. The CVSS vector rates confidentiality high, with no integrity or availability impact.

Likely exposure

Exposure is most likely in environments running Keylime versions before 6.3.0, especially systems installed with the affected installer and containing secrets in keylime.conf. The bundled affected-version data is inconsistent, so confirm against the vendor advisory.

Exploitation context

The provided sources do not cite active exploitation, and the CVE is not marked KEV. Practical impact depends on what sensitive data is present in keylime.conf and whether unauthorized users or processes can read it.

Researcher notes

The key uncertainty is scope: the CVE text says before 6.3.0, while the bundled affected field lists 6.3.0. Use the GitHub advisory and fixing commit as the authoritative remediation context, and avoid claiming exploitation without additional evidence.

Mitigation direction

  • Review the Keylime advisory for the supported fixed release guidance.
  • Upgrade Keylime to 6.3.0 or later where applicable.
  • Inspect keylime.conf permissions and restrict access per vendor guidance.
  • Rotate any secrets that may have been exposed from keylime.conf.
  • Document remediation status for affected Keylime hosts.

Validation and detection

  • Inventory Keylime versions across managed hosts.
  • Identify systems installed before the 6.3.0 fix.
  • Check whether keylime.conf is world-readable.
  • Review keylime.conf for sensitive values requiring rotation.
  • Confirm permissions remain restricted after upgrades or reinstalls.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookup
cve · low confidence lookup

CVE-2022-23952 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

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

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-23952Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/akeylimekeylime 6.3.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.