Security readout for executives and security teams
Plain-English summary
CVE-2025-1057 is an availability issue in Keylime. After upgrading the registrar to 7.12.0, older database records may be unreadable because their stored type differs. The result is failed agent registration processing, which can interrupt remote attestation workflows rather than expose data.
Executive priority
Treat this as a moderate operational reliability issue for environments relying on Keylime attestation. Prioritize upgrade testing and vendor remediation tracking if Keylime supports compliance, trusted boot validation, or workload admission decisions.
Technical view
Keylime 7.12.0 introduced strict type checking that expects agent registration data as str. Records created by earlier versions, such as 7.11.0, may store the same data as bytes. When the registrar processes affected registration requests, it can raise an exception and the agent fails.
Likely exposure
Exposure is most likely in Keylime deployments upgraded to 7.12.0 while retaining registrar database entries created by older versions. The bundle lists Red Hat Enterprise Linux 9 and 10 with default status unaffected, so RHEL exposure is not established here.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The described failure depends on incompatible legacy database content being processed during agent registration. This is a denial-of-service style operational risk, not a confidentiality or integrity issue.
Researcher notes
The issue is CWE-704, incorrect type conversion or cast. The evidence points to an upgrade compatibility flaw between bytes and str representations in registrar data. No exploit details, public weaponization, or confirmed patch are provided in the bundle.
Mitigation direction
- Check Red Hat and upstream Keylime guidance for fixed packages or migration instructions.
- Test Keylime 7.12.0 upgrades against a copy of the registrar database first.
- Back up registrar data before version changes or data-format migration.
- Monitor registrar logs for exceptions during agent registration after upgrade.
- Avoid production upgrade paths that leave incompatible legacy records unhandled.
Validation and detection
- Confirm whether Keylime registrar version 7.12.0 is deployed.
- Identify whether registrar database records were created by pre-7.12.0 versions.
- Review agent registration failures after upgrade windows.
- Check vendor advisories for affected build and remediation status.
- Verify RHEL 9 or 10 status against Red Hat’s CVE entry.
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-704: 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-1057 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
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.
SSVC decision data
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:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L2.81.4redhatVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2025-1057CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2343894CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/ansasaki/keylime/tree/base64_bytesCVE reference, redhat
- https://github.com/keylime/rust-keylimeCVE reference, redhat
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.
Incorrect Type Conversion or Cast
Incorrect Type Conversion or Cast represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.