{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-37479 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-37479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-37479 is a medium-severity vulnerability in openenclave, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-37479 and fix it if it is affected.\n\nWhat it is: CVE-2023-37479 is a medium-severity vulnerability in openenclave, published on 17 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-37479 in the wild and no public exploit code.\n\nAffected product: openenclave. 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-37479/ (Markdown: https://insights.sbomify.com/CVE-2023-37479/index.md)","id":"CVE-2023-37479","markdown":"https://insights.sbomify.com/CVE-2023-37479/index.md","name":"CVE-2023-37479","record":{"aliases":["GHSA-5gfr-m6mx-p5w4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Open Enclave SDK","requires_auth":"none","summary":"Attackers can exploit unsanitized CPU registers in Open Enclave to perform side-channel attacks and leak sensitive data from enclaves.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openenclave","vendor":"openenclave"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"}],"description":"Open Enclave is a hardware-agnostic open source library for developing applications that utilize Hardware-based Trusted Execution Environments, also known as Enclaves. There are two issues that are mitigated in version 0.19.3. First, Open Enclave SDK does not properly sanitize the `MXCSR` register on enclave entry. This makes applications vulnerable to MXCSR Configuration Dependent Timing (MCDT) attacks, where incorrect `MXCSR` values can impact instruction retirement by at most one cycle, depending on the (secret) data operand value. Please find more details in the guidance from Intel in the references. Second, Open Enclave SDK does not sanitize x86's alignment check flag `RFLAGS.AC` on enclave entry. This opens up the possibility for a side-channel attacker to be notified for every unaligned memory access performed by the enclave. The issue has been addressed in version 0.19.3 and the current master branch. Users will need to recompile their applications against the patched libraries to be protected from this vulnerability. There are no known workarounds for this vulnerability.","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":"Improper sanitization of MXCSR and RFLAGS in OpenEnclave","id":"CVE-2023-37479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Fides Webserver Vulnerable to Zip Bomb File Uploads","id":"CVE-2023-37480"},"packages":[],"prev":{"headline":"pnpm incorrectly parses tar archives relative to specification","id":"CVE-2023-37478"},"products":["openenclave"],"published":"2023-07-17","related":[{"cvss_score":6.8,"headline":"Socket syscalls can leak enclave memory contents in Open Enclave","id":"CVE-2020-15224","kev_date_added":null,"published":"2020-10-14"},{"cvss_score":5.3,"headline":"x87 FPU operations in enclaves are vulnerable to ABI poisoning in openenclave","id":"CVE-2020-15107","kev_date_added":null,"published":"2020-07-15"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["openenclave"]},"summary":"Attackers can exploit unsanitized CPU registers in Open Enclave to perform side-channel attacks and leak sensitive data from enclaves.","url":"https://insights.sbomify.com/CVE-2023-37479/"}