Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

Keylime: unhandled exceptions could lead to invalid attestation states

CVE-2022-3500GHSA-hff2-x2j9-gxgv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (keylime 6.5.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI keylime

    Affected
    < 6.5.1
    Fixed in
    6.5.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2022-3500: 0.27% estimated exploitation activity in the next 30 days; percentile 18.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact This vulnerability creates a false sense of security for keylime users -- i.e. a user could query keylime and conclude that a parcitular node/agent is correctly attested, while attestations are not in fact taking place. Short explanation: the keylime verifier creates periodic reports on the state of each attested agent. The keylime verifier runs a set of python asynchronous processes to challenge attested nodes and create reports on the outcome. The vulnerability consists of the above named python asynchronous processes failing silently, i.e. quitting without leaving behind a database entry, raising an error or producing even a mention of an error in a log. The silent failure can be triggered by a small set of transient network failure conditions; recoverable device driver crashes being one such condition we saw in the wild. Patches The problem is fixed in keylime starting with tag 6.5.1 Workarounds This patch can be retroactively applied to any running keylime deployment.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-hff2-x2j9-gxgv

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-hff2-x2j9-gxgv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-3500

Advisory: Keylime: unhandled exceptions could lead to invalid attestation states
IDs: CVE-2022-3500, GHSA-hff2-x2j9-gxgv
Record: https://patchnext.com/advisories/cve-2022-3500 (revision 3, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: keylime 6.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI keylime: affected < 6.5.1; fixed in 6.5.1

## Suggested inspection (read-only)
- `python -m pip show keylime`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on keylime.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hff2-x2j9-gxgv (OSV record GHSA-hff2-x2j9-gxgv lists affected ranges: PyPI keylime >=0 <6.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-hff2-x2j9-gxgv (GitHub-reviewed advisory GHSA-hff2-x2j9-gxgv lists affected ranges: PyPI keylime >=0 <6.5.1)

Commands are suggestions: review each one before running it.

Loading voting…