{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20135 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20135 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20135 is a high-severity vulnerability in n/a, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20135 and fix it if it is affected.\n\nWhat it is: CVE-2018-20135 is a high-severity vulnerability in n/a, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-20135 in the wild and no public exploit code.\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-20135/ (Markdown: https://insights.sbomify.com/CVE-2018-20135/index.md)","id":"CVE-2018-20135","markdown":"https://insights.sbomify.com/CVE-2018-20135/index.md","name":"CVE-2018-20135","record":{"aliases":["GHSA-3wcx-33v7-xf78"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Galaxy Apps","requires_auth":"none","summary":"Attackers can bypass SSL and signature checks to inject malicious code during app installation via man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"galaxy_apps","vendor":"samsung"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Samsung Galaxy Apps before 4.4.01.7 allows modification of the hostname used for load balancing on installations of applications through a man-in-the-middle attack. An attacker may trick Galaxy Apps into using an arbitrary hostname for which the attacker can provide a valid SSL certificate, and emulate the API of the app store to modify existing apps at installation time. The specific flaw involves an HTTP method to obtain the load-balanced hostname that enforces SSL only after obtaining a hostname from the load balancer, and a missing app signature validation in the application XML. An attacker can exploit this vulnerability to achieve Remote Code Execution on the device. The Samsung ID is SVE-2018-12071.","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":"Security feature bypass in n/a","id":"CVE-2018-20135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-20136"},"packages":[],"prev":{"headline":"Code injection in ymlref","id":"CVE-2018-20133"},"products":["n/a"],"published":"2019-06-07","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Samsung Galaxy Apps","id":"CVE-2018-10502","kev_date_added":null,"published":"2018-09-24"},{"cvss_score":7,"headline":"Code injection in Samsung Galaxy Apps","id":"CVE-2018-10499","kev_date_added":null,"published":"2018-09-24"},{"cvss_score":7,"headline":"Privilege escalation in Samsung Galaxy Apps","id":"CVE-2018-10500","kev_date_added":null,"published":"2018-09-24"}],"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-05","vendors":["n/a"]},"summary":"Attackers can bypass SSL and signature checks to inject malicious code during app installation via man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2018-20135/"}