{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3903 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3903 is a critical memory corruption vulnerability in Talos Samsung, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-3903 and fix it if it is affected.\n\nWhat it is: CVE-2018-3903 is a critical memory corruption vulnerability in Talos Samsung, published on 23 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-3903 in the wild and no public exploit code.\n\nAffected product: Talos Samsung. 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-2018-3903/ (Markdown: https://insights.sbomify.com/CVE-2018-3903/index.md)","id":"CVE-2018-3903","markdown":"https://insights.sbomify.com/CVE-2018-3903/index.md","name":"CVE-2018-3903","record":{"aliases":["GHSA-rfq8-x5m9-6822"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SmartThings Hub","requires_auth":"low_privilege","summary":"A stack buffer overflow in the video-core process allows remote code execution via a crafted HTTP request on Samsung SmartThings Hub devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"sth-eth-250_firmware","vendor":"samsung"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"On Samsung SmartThings Hub STH-ETH-250 devices with firmware version 0.20.17, the video-core process incorrectly extracts fields from a user-controlled JSON payload, leading to a buffer overflow on the stack. An attacker can send an HTTP request to trigger this vulnerability. The memcpy call overflows the destination buffer, which has a size of 512 bytes. An attacker can send an arbitrarily long \"url\" value in order to overwrite the saved-PC with 0x42424242.","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":"Memory corruption in Samsung","id":"CVE-2018-3903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Samsung","id":"CVE-2018-3904"},"packages":[],"prev":{"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3902"},"products":["Samsung"],"published":"2018-08-23","related":[{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3873","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3874","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3876","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3877","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3894","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3864","kev_date_added":null,"published":"2018-09-20"},{"cvss_score":9.9,"headline":"Memory corruption in SmartThings Hub STH-ETH-250","id":"CVE-2018-3865","kev_date_added":null,"published":"2018-09-20"}],"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-09-17","vendors":["Talos"]},"summary":"A stack buffer overflow in the video-core process allows remote code execution via a crafted HTTP request on Samsung SmartThings Hub devices.","url":"https://insights.sbomify.com/CVE-2018-3903/"}