dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-3500

MEDIUM · 5.1 CVSS v3.1 Published 2022-11-22
Fix available
A fix is available. Upgrade to 6.5.1 or later.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click Patch available

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 · unedited
A vulnerability was found in keylime. This security issue happens in some circumstances, due to some improperly handled exceptions, there exists the possibility that a rogue agent could create errors on the verifier that stopped attestation attempts for that host leaving it in an attested state but not verifying that anymore.

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

A detailed technical summary for this CVE is being prepared.

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
Enterprise LinuxOperating system
Affected:= 9.0
FedoraOperating system
Affected:= 35= 36= 37
KeylimeApplication
Affected:< 6.5.1

CVSS 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
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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.

dbcve · scoped
Upgrade available Upgrade to 6.5.1 or later
Fixed in 6.5.1
Vendor patch github.com →
Recommended fix High confidence

Keylime 6.5.1 or later

  1. 1. Check the current installed version of Keylime: rpm -qa | grep keylime or keylime_verifier --version
  2. 2. Backup your Keylime configuration files (typically in /etc/keylime/)
  3. 3. Update your package repository to ensure you have access to the latest packages
  4. 4. Upgrade Keylime packages to version 6.5.1 or later using your package manager (dnf update keylime)
  5. 5. For RHEL/Enterprise Linux 9.0: Ensure you have the latest errata or update channel applied
  6. 6. For Fedora 35-37: Apply all pending system updates which will include the fixed Keylime packages
  7. 7. Verify the new version is installed: rpm -qa | grep keylime
  8. 8. Review the Keylime 6.5.1 release notes for any configuration or behavioral changes
Caveat Review Keylime 6.5.1 release notes for any configuration or behavioral changes; minor config adjustments may be needed

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3500 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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