{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15224 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15224 is a medium-severity vulnerability in openenclave, published on 14 Oct 2020. 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-2020-15224 and fix it if it is affected.\n\nWhat it is: CVE-2020-15224 is a medium-severity vulnerability in openenclave, published on 14 Oct 2020. 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-2020-15224 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-2020-15224/ (Markdown: https://insights.sbomify.com/CVE-2020-15224/index.md)","id":"CVE-2020-15224","markdown":"https://insights.sbomify.com/CVE-2020-15224/index.md","name":"CVE-2020-15224","record":{"aliases":["GHSA-525h-wxcc-f66m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Open Enclave SDK","requires_auth":"low_privilege","summary":"A malicious host can read privileged enclave memory via socket syscalls, exposing confidential data to attackers with local access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openenclave","vendor":"openenclave"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"}],"description":"In Open Enclave before version 0.12.0, an information disclosure vulnerability exists when an enclave application using the syscalls provided by the sockets.edl is loaded by a malicious host application. An attacker who successfully exploited the vulnerability could read privileged data from the enclave heap across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information otherwise considered confidential in an enclave, which could be used in further compromises. The issue has been addressed in version 0.12.0 and the current master branch. Users will need to to recompile their applications against the patched libraries to be protected from 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":"Socket syscalls can leak enclave memory contents in Open Enclave","id":"CVE-2020-15224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of Service vulnerability in django-filter","id":"CVE-2020-15225"},"packages":[],"prev":{"headline":"Ignored storage errors on token revokation in ORY Fosite","id":"CVE-2020-15223"},"products":["openenclave"],"published":"2020-10-14","related":[{"cvss_score":5.3,"headline":"Improper sanitization of MXCSR and RFLAGS in OpenEnclave","id":"CVE-2023-37479","kev_date_added":null,"published":"2023-07-17"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["openenclave"]},"summary":"A malicious host can read privileged enclave memory via socket syscalls, exposing confidential data to attackers with local access.","url":"https://insights.sbomify.com/CVE-2020-15224/"}