{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-10751 exists.","fix":"No fix has been published for CVE-2018-10751 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10751 is a medium-severity vulnerability in n/a, published on 29 May 2018. 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-2018-10751 and fix it if it is affected.\n\nWhat it is: CVE-2018-10751 is a medium-severity vulnerability in n/a, published on 29 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-10751 exists.\n\nAffected product: n/a. 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-10751/ (Markdown: https://insights.sbomify.com/CVE-2018-10751/index.md)","id":"CVE-2018-10751","markdown":"https://insights.sbomify.com/CVE-2018-10751/index.md","name":"CVE-2018-10751","record":{"aliases":["GHSA-p6q3-c5p7-24j9"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung S7 Edge","requires_auth":"none","summary":"A malformed WAP push message triggers an integer overflow in memory allocation, leading to memory corruption and potential code execution on Samsung S7 Edge devices.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"samsung_mobile","vendor":"samsung"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml payload. This is due to an integer overflow in memory allocation for this string. The Samsung ID is SVE-2018-11463.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-05-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-05-23","kind":"exploitdb","ref":"44724","stars":null,"title":"Samsung Galaxy S7 Edge - Overflow in OMACP WbXml String Extension Processing"}],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in n/a","id":"CVE-2018-10751","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-10752"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-10750"},"products":["n/a"],"published":"2018-05-29","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-9139","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-9143","kev_date_added":null,"published":"2018-03-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-5538","kev_date_added":null,"published":"2017-03-23"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9965","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9966","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2016-9967","kev_date_added":null,"published":"2016-12-16"},{"cvss_score":8.4,"headline":"Memory corruption in n/a","id":"CVE-2017-18020","kev_date_added":null,"published":"2018-01-04"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A malformed WAP push message triggers an integer overflow in memory allocation, leading to memory corruption and potential code execution on Samsung S7 Edge devices.","url":"https://insights.sbomify.com/CVE-2018-10751/"}