{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15137 is a medium-severity vulnerability in jwise HoRNDIS, published on 12 Aug 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-15137 and fix it if it is affected.\n\nWhat it is: CVE-2020-15137 is a medium-severity vulnerability in jwise HoRNDIS, published on 12 Aug 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15137 in the wild and no public exploit code.\n\nAffected product: jwise HoRNDIS. 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-15137/ (Markdown: https://insights.sbomify.com/CVE-2020-15137/index.md)","id":"CVE-2020-15137","markdown":"https://insights.sbomify.com/CVE-2020-15137/index.md","name":"CVE-2020-15137","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS USB driver","requires_auth":"low_privilege","summary":"A malicious USB device can trigger an integer overflow in HoRNDIS, leading to kernel memory disclosure or system crashes on macOS hosts.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"horndis","vendor":"horndis_project"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"All versions of HoRNDIS are affected by an integer overflow in the RNDIS packet parsing routines. A malicious USB device can trigger disclosure of unrelated kernel memory to userspace applications on the host, or can cause the kernel to crash. Kernel memory disclosure is especially likely on 32-bit kernels; 64-bit kernels are more likely to crash on attempted exploitation. It is not believed that kernel memory corruption is possible, or that unattended kernel memory disclosure without the collaboration of a userspace program running on the host is possible. The vulnerability is in `HoRNDIS::receivePacket`. `msg_len`, `data_ofs`, and `data_len` can be controlled by an attached USB device, and a negative value of `data_ofs` can bypass the check for `(data_ofs + data_len + 8) \u003e msg_len`, and subsequently can cause a wild pointer copy in the `mbuf_copyback` call. The software is not maintained and no patches are planned. Users of multi-tenant systems with HoRNDIS installed should only connect trusted USB devices to their system.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Integer overflow in HoRNDIS","id":"CVE-2020-15137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-Site Scripting in Prism","id":"CVE-2020-15138"},"packages":[],"prev":{"headline":"Improper authentication in etcd","id":"CVE-2020-15136"},"products":["HoRNDIS"],"published":"2020-08-12","related":[],"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":["jwise"]},"summary":"A malicious USB device can trigger an integer overflow in HoRNDIS, leading to kernel memory disclosure or system crashes on macOS hosts.","url":"https://insights.sbomify.com/CVE-2020-15137/"}