{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5138 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5138 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5138 is a medium-severity vulnerability in silabs.com GSDK, published on 3 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5138 and fix it if it is affected.\n\nWhat it is: CVE-2023-5138 is a medium-severity vulnerability in silabs.com GSDK, published on 3 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-5138 in the wild and no public exploit code.\n\nAffected product: silabs.com GSDK. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-5138/ (Markdown: https://insights.sbomify.com/CVE-2023-5138/index.md)","id":"CVE-2023-5138","markdown":"https://insights.sbomify.com/CVE-2023-5138/index.md","name":"CVE-2023-5138","record":{"aliases":["GHSA-32h2-7245-4mh4"],"analysis":{"component_type":"hardware_firmware","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Silicon Labs Secure Vault","requires_auth":"none","summary":"Attackers can bypass glitch detection protections on Silicon Labs Secure Vault High devices because the feature is disabled by default.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Silabs","cpe":[{"product":"gecko_software_development_kit","vendor":"silabs"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-909","name":"Missing Initialization of Resource"},{"id":"CWE-1319","name":"Improper Protection against Electromagnetic Fault Injection (EM-FI)"}],"description":"Glitch detection is not enabled by default for the CortexM33 core in Silicon Labs secure vault high parts EFx32xG2xB, except EFR32xG21B.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Glitch detection not active by default in Silicon Labs Secure Vault High devices","id":"CVE-2023-5138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Potential buffer overflow vulnerability in the Zephyr STM32 Crypto driver","id":"CVE-2023-5139"},"packages":[],"prev":{"headline":"Simply Excerpts \u003c= 1.4 - Admin+ Stored XSS","id":"CVE-2023-5137"},"products":["GSDK"],"published":"2024-01-03","related":[{"cvss_score":10,"headline":"Memory corruption in Gecko Platform","id":"CVE-2023-45318","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":9.8,"headline":"Memory corruption in Gecko Platform","id":"CVE-2023-2686","kev_date_added":null,"published":"2023-06-15"},{"cvss_score":9.3,"headline":"Unvalidated input in Silicon Labs TrustZone implementation leads to accessing Trusted memory region","id":"CVE-2023-4280","kev_date_added":null,"published":"2024-01-02"},{"cvss_score":9,"headline":"Unvalidated input in Silicon Labs PSA Attestation service leads to secure memory access from non-secure memory","id":"CVE-2023-4020","kev_date_added":null,"published":"2023-12-15"},{"cvss_score":9,"headline":"Memory corruption in Cesium NET","id":"CVE-2023-25181","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":9,"headline":"Memory corruption in Cesium NET","id":"CVE-2023-27882","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":9,"headline":"Memory corruption in Cesium NET","id":"CVE-2023-28379","kev_date_added":null,"published":"2023-11-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-03","vendors":["silabs.com"]},"summary":"Attackers can bypass glitch detection protections on Silicon Labs Secure Vault High devices because the feature is disabled by default.","url":"https://insights.sbomify.com/CVE-2023-5138/"}