GHSA-x9mp-jm4h-jjf8: Duplicate Advisory EVE Doesn't Protect Rootfs Vulnerability

HIGH
CVSS 8.8
CWE-345
Published
Advisory Summary

GHSA-x9mp-jm4h-jjf8 is a HIGH (CVSS 8.8) eve doesn't protect rootfs vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Duplicate Advisory libraries in the Go ecosystem. The issue involves eve doesn't protect rootfs. Remediation is available by upgrading affected packages to version 0.0.0-20220708121648-5fef4d92e758.

GHSA-x9mp-jm4h-jjf8 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-x9mp-jm4h-jjf8
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
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-x9mp-jm4h-jjf8

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/pkg/grub fixed: 0.0.0-20220708121648-5fef4d92e758
Upgrade github.com/lf-edge/eve/pkg/grub to 0.0.0-20220708121648-5fef4d92e758
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/pkg/grub

How to Check if You Are Affected

To determine whether your application is affected by GHSA-x9mp-jm4h-jjf8, inspect your project dependencies for Duplicate Advisory:

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

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-20220708121648-5fef4d92e758), 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-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. 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 In EVE OS, the “measured boot” mechanism prevents a compromised device from accessing the encrypted data located in the vault. As per the “measured boot” design, the PCR values calculated at different stages of the boot process will change if any of their respective parts are changed. This includes, among other things, the configuration of the bios, grub, the kernel cmdline, initrd, and more. However, this mechanism does not validate the entire rootfs, so an attacker can edit the filesystem and gain control over the system. As the default filesystem used by EVE OS is squashfs, this is somewhat harder than an ext4, which is easily changeable. This will not stop an attacker, as an attacker can repackage the squashfs with their changes in it and replace the partition altogether. This can also be done directly on the device, as the “003-storage-init” container contains the “mksquashfs” and “unsquashfs” binaries (with the corresponding libs). An attacker can gain full control over the device without changing the PCR values, thus not triggering the “measured boot” mechanism, and having full access to the vault. Note: This issue was partially fixed in these commits (after disclosure to Zededa), where the config partition measurement was added to PCR13: • aa3501d6c57206ced222c33aea15a9169d629141 • 5fef4d92e75838cc78010edaed5247dfbdae1889. This issue was made viable in version 9.0.0 when the calculation was moved to PCR14 but it was not included in the measured boot.

GHSA-x9mp-jm4h-jjf8 Affected Duplicate Advisory Versions

1 component(s)
Fixed Versions:
0.0.0-20220708121648-5fef4d92e758
Product / Package Ecosystem Affected Versions Fixed Version
github.com/lf-edge/eve/pkg/grub
Go
< 0.0.0-20220708121648-5fef4d92e758
0.0.0-20220708121648-5fef4d92e758

References

Frequently Asked Questions

What is GHSA-x9mp-jm4h-jjf8?
GHSA-x9mp-jm4h-jjf8 is a security vulnerability in Duplicate Advisory involving EVE Doesn't Protect Rootfs under CWE-345: Insufficient Verification of Data Authenticity.
Which Duplicate Advisory versions are affected?
Affected versions include releases prior to 0.0.0-20220708121648-5fef4d92e758 across affected packages: github.com/lf-edge/eve/pkg/grub.
What version fixes GHSA-x9mp-jm4h-jjf8?
Upgrading to 0.0.0-20220708121648-5fef4d92e758 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lf-edge/eve/pkg/grub affected?
Yes, github.com/lf-edge/eve/pkg/grub is affected in releases prior to 0.0.0-20220708121648-5fef4d92e758. Upgrade your dependency to 0.0.0-20220708121648-5fef4d92e758 or later.
What is the CVSS score of GHSA-x9mp-jm4h-jjf8?
GHSA-x9mp-jm4h-jjf8 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-x9mp-jm4h-jjf8?
GHSA-x9mp-jm4h-jjf8 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Go dependencies for GHSA-x9mp-jm4h-jjf8?
Run the dependency tree command: 'inspect dependencies for github.com/lf-edge/eve/pkg/grub'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x9mp-jm4h-jjf8",
  "modified" : "2026-02-04T23:14:16Z",
  "published" : "2023-09-20T15:30:52Z",
  "withdrawn" : "2026-02-04T23:14:16Z",
  "aliases" : [ ],
  "summary" : "Duplicate Advisory: EVE Doesn't Protect Rootfs",
  "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\nIn EVE OS, the “measured boot” mechanism prevents a compromised device from accessing\nthe encrypted data located in the vault.\n\nAs per the “measured boot” design, the PCR values calculated at different stages of the boot\nprocess will change if any of their respective parts are changed.\n\nThis includes, among other things, the configuration of the bios, grub, the kernel cmdline,\ninitrd, and more.\n\nHowever, this mechanism does not validate the entire rootfs, so an attacker can edit the\nfilesystem and gain control over the system.\n\nAs the default filesystem used by EVE OS is squashfs, this is somewhat harder than an ext4,\nwhich is easily changeable.\n\nThis will not stop an attacker, as an attacker can repackage the squashfs with their changes\nin it and replace the partition altogether.\n\nThis can also be done directly on the device, as the “003-storage-init” container contains the\n“mksquashfs” and “unsquashfs” binaries (with the corresponding libs).\n\n\n\n\n\n\n\nAn attacker can gain full control over the device without changing the PCR values, thus not\ntriggering the “measured boot” mechanism, and having full access to the vault.\n\n\n\nNote:\n\nThis issue was partially fixed in these commits (after disclosure to Zededa), where the config\npartition measurement was added to PCR13:\n\n• aa3501d6c57206ced222c33aea15a9169d629141\n\n• 5fef4d92e75838cc78010edaed5247dfbdae1889.\n\nThis issue was made viable in version 9.0.0 when the calculation was moved to PCR14 but it was not included in the measured boot.",
  "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/pkg/grub"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20220708121648-5fef4d92e758"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-43636"
  }, {
    "type" : "WEB",
    "url" : "https://asrg.io/security-advisories/19274"
  }, {
    "type" : "WEB",
    "url" : "https://asrg.io/security-advisories/cve-2023-43636"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-04T23:14:16Z",
    "nvd_published_at" : "2023-09-20T15:15:12Z"
  }
}