GHSA-h929-fvvp-882c: Duplicate Advisory EVE Seals Vault Key With Vulnerability

HIGH
Share
CVSS 8.8
CWE-327 CWE-328
Published
Advisory Summary

GHSA-h929-fvvp-882c is a HIGH (CVSS 8.8) eve seals vault key with vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Duplicate Advisory libraries in the Go ecosystem. The issue involves eve seals vault key with sha1 pcrs. Remediation is available by upgrading affected packages to version 0.0.0-20230519072751-977f42b07fa9.

GHSA-h929-fvvp-882c at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-h929-fvvp-882c
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Duplicate Advisory
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-h929-fvvp-882c

To remediate this vulnerability, upgrade all affected Duplicate Advisory dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/lf-edge/eve fixed: 0.0.0-20230519072751-977f42b07fa9 
Upgrade github.com/lf-edge/eve to 0.0.0-20230519072751-977f42b07fa9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/lf-edge/eve

How to Check if You Are Affected

To determine whether your application is affected by GHSA-h929-fvvp-882c, inspect your project dependencies for Duplicate Advisory:

inspect dependencies for github.com/lf-edge/eve

Analyze the terminal output to locate any version of Duplicate Advisory in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20230519072751-977f42b07fa9), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Duplicate Advisory, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-wc42-fcjp-v8vq. This link is maintained to preserve external references. ### Original Description Vault Key Sealed With SHA1 PCRs The measured boot solution implemented in EVE OS leans on a PCR locking mechanism. Different parts of the system update different PCR values in the TPM, resulting in a unique value for each PCR entry. These PCRs are then used in order to seal/unseal a key from the TPM which is used to encrypt/decrypt the “vault” directory. This “vault” directory is the most sensitive point in the system and as such, its content should be protected. This mechanism is noted in Zededa’s documentation as the “measured boot” mechanism, designed to protect said “vault”. The code that’s responsible for generating and fetching the key from the TPM assumes that SHA256 PCRs are used in order to seal/unseal the key, and as such their presence is being checked. The issue here is that the key is not sealed using SHA256 PCRs, but using SHA1 PCRs. This leads to several issues: • Machines that have their SHA256 PCRs enabled but SHA1 PCRs disabled, as well as not sealing their keys at all, meaning the “vault” is not protected from an attacker. • SHA1 is considered insecure and reduces the complexity level required to unseal the key in machines which have their SHA1 PCRs enabled. An attacker can very easily retrieve the contents of the “vault”, which will effectively render the “measured boot” mechanism meaningless.

GHSA-h929-fvvp-882c Affected Duplicate Advisory Versions

1 component(s)
Fixed Versions:
0.0.0-20230519072751-977f42b07fa9
Product / Package Ecosystem Affected Versions Fixed Version
github.com/lf-edge/eve
golang/github.com/lf-edge/eve
Go
< 0.0.0-20230519072751-977f42b07fa9
0.0.0-20230519072751-977f42b07fa9

References

NVD — GHSA-h929-fvvp-882c NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-43635
Duplicate Advisory Security Information SECURITY
https://asrg.io/security-advisories/cve-2023-43635
Duplicate Advisory Security Information SECURITY
https://asrg.io/security-advisories/vault-key-sealed-with-sha1-pcrs

Frequently Asked Questions

What is GHSA-h929-fvvp-882c?
GHSA-h929-fvvp-882c is a security vulnerability in Duplicate Advisory involving EVE Seals Vault Key With SHA1 PCRs under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Duplicate Advisory versions are affected?
Affected versions include releases prior to 0.0.0-20230519072751-977f42b07fa9 across affected packages: github.com/lf-edge/eve.
What version fixes GHSA-h929-fvvp-882c?
Upgrading to 0.0.0-20230519072751-977f42b07fa9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lf-edge/eve affected?
Yes, github.com/lf-edge/eve is affected in releases prior to 0.0.0-20230519072751-977f42b07fa9. Upgrade your dependency to 0.0.0-20230519072751-977f42b07fa9 or later.
What is the CVSS score of GHSA-h929-fvvp-882c?
GHSA-h929-fvvp-882c has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with GHSA-h929-fvvp-882c?
GHSA-h929-fvvp-882c is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check Go dependencies for GHSA-h929-fvvp-882c?
Run the dependency tree command: 'inspect dependencies for github.com/lf-edge/eve'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h929-fvvp-882c",
  "modified" : "2026-02-04T23:11:53Z",
  "published" : "2023-09-20T15:30:52Z",
  "withdrawn" : "2026-02-04T23:11:53Z",
  "aliases" : [ ],
  "summary" : "Duplicate Advisory: EVE Seals Vault Key With SHA1 PCRs",
  "details" : "### Duplicate Advisory\nThis advisory has been withdrawn because it is a duplicate of GHSA-wc42-fcjp-v8vq. This link is maintained to preserve external references.\n\n### Original Description\nVault Key Sealed With SHA1 PCRs\n\n\n\n\n\n\nThe measured boot solution implemented in EVE OS leans on a PCR locking mechanism.\n\nDifferent parts of the system update different PCR values in the TPM, resulting in a unique\nvalue for each PCR entry.\n\nThese PCRs are then used in order to seal/unseal a key from the TPM which is used to\nencrypt/decrypt the “vault” directory.\n\nThis “vault” directory is the most sensitive point in the system and as such, its content should\nbe protected.\n\nThis mechanism is noted in Zededa’s documentation as the “measured boot” mechanism,\ndesigned to protect said “vault”.\n\nThe code that’s responsible for generating and fetching the key from the TPM assumes that\nSHA256 PCRs are used in order to seal/unseal the key, and as such their presence is being\nchecked.\n\nThe issue here is that the key is not sealed using SHA256 PCRs, but using SHA1 PCRs.\nThis leads to several issues:\n\n• Machines that have their SHA256 PCRs enabled but SHA1 PCRs disabled, as well\nas not sealing their keys at all, meaning the “vault” is not protected from an attacker.\n\n• SHA1 is considered insecure and reduces the complexity level required to unseal the\nkey in machines which have their SHA1 PCRs enabled.\n\n\n\nAn attacker can very easily retrieve the contents of the “vault”, which will effectively render\nthe “measured boot” mechanism meaningless.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lf-edge/eve"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20230519072751-977f42b07fa9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-43635"
  }, {
    "type" : "WEB",
    "url" : "https://asrg.io/security-advisories/cve-2023-43635"
  }, {
    "type" : "WEB",
    "url" : "https://asrg.io/security-advisories/vault-key-sealed-with-sha1-pcrs"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327", "CWE-328" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-04T23:11:53Z",
    "nvd_published_at" : "2023-09-20T15:15:11Z"
  }
}