# CVE-2023-43630: Config Partition Not Measured From 2 Fronts > Attackers can modify the config partition without triggering measured boot, gaining full device control and access to encrypted vault contents. - **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Sep 2023 - **Updated:** 24 Sep 2024 - **Also known as:** GHSA-phcg-h58r-gmcq, GO-2026-4430 ## What is CVE-2023-43630? CVE-2023-43630 is a high-severity vulnerability in EVE OS, published on 20 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description PCR14 is not in the list of PCRs that seal/unseal the “vault” key, but due to the change that was implemented in commit “7638364bc0acf8b5c481b5ce5fea11ad44ad7fd4”, fixing this issue alone would not solve the problem of the config partition not being measured correctly. Also, the “vault” key is sealed/unsealed with SHA1 PCRs instead of SHA256. This issue was somewhat mitigated due to all of the PCR extend functions updating both the values of SHA256 and SHA1 for a given PCR ID. However, due to the change that was implemented in commit “7638364bc0acf8b5c481b5ce5fea11ad44ad7fd4”, this is no longer the case for PCR14, as the code in “measurefs.go” explicitly updates only the SHA256 instance of PCR14, which means that even if PCR14 were to be added to the list of PCRs sealing/unsealing the “vault” key, changes to the config partition would still not be measured. An attacker could modify the config partition without triggering the measured boot, this could result in the attacker gaining full control over the device with full access to the contents of the encrypted “vault” Weakness: CWE-922 (Insecure Storage of Sensitive Information), CWE-522 (Insufficiently Protected Credentials), CWE-328 (Use of Weak Hash) ## Which versions are affected by CVE-2023-43630? 3 open source packages ship an affected version, including github.com/lf-edge/eve. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/lf-edge/eve` | Go | All versions | 0.0.0-20230126065759-d9383a7ee4e1 | | `github.com/lf-edge/eve` | Go | All versions | 0.0.0-20230126065759-d9383a7ee4e1 | | `github.com/lf-edge/eve` | Go | All versions | 0.0.0-20230126065759-d9383a7ee4e1 | Products: Linuxfoundation Edge Virtualization Engine. ## How do I fix CVE-2023-43630? Upgrade github.com/lf-edge/eve to 0.0.0-20230126065759-d9383a7ee4e1 or later. ## Is CVE-2023-43630 being exploited? There is no known exploitation of CVE-2023-43630 in the wild and no public exploit code. ## Other vulnerabilities in EVE OS - [CVE-2023-43632](https://insights.sbomify.com/CVE-2023-43632/): Freely Allocate Buffer on The Stack With Data From Socket (critical 9.0) - [CVE-2023-43631](https://insights.sbomify.com/CVE-2023-43631/): SSH as Root Unlockable Without Triggering Measured Boot (high 8.8) - [CVE-2023-43635](https://insights.sbomify.com/CVE-2023-43635/): Vault Key Sealed With SHA1 PCRs (high 8.8) - [CVE-2023-43636](https://insights.sbomify.com/CVE-2023-43636/): Rootfs Not Protected (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-43630 and fix it if it is affected. What it is: CVE-2023-43630 is a high-severity vulnerability in EVE OS, published on 20 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-43630 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/lf-edge/eve (Go): affected all versions; fixed in 0.0.0-20230126065759-d9383a7ee4e1 - github.com/lf-edge/eve (Go): affected all versions; fixed in 0.0.0-20230126065759-d9383a7ee4e1 - github.com/lf-edge/eve (Go): affected all versions; fixed in 0.0.0-20230126065759-d9383a7ee4e1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-43630/ (Markdown: https://insights.sbomify.com/CVE-2023-43630/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-43630 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-43630 - OSV: https://osv.dev/vulnerability/CVE-2023-43630 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-43630/ Summaries are generated and may contain mistakes; the official description above is the record.