{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26244 exists.","fix":"No fix has been published for CVE-2023-26244 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26244 is a high-severity vulnerability in n/a, published on 27 Apr 2023. 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-2023-26244 and fix it if it is affected.\n\nWhat it is: CVE-2023-26244 is a high-severity vulnerability in n/a, published on 27 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26244 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-2023-26244/ (Markdown: https://insights.sbomify.com/CVE-2023-26244/index.md)","id":"CVE-2023-26244","markdown":"https://insights.sbomify.com/CVE-2023-26244/index.md","name":"CVE-2023-26244","record":{"aliases":["GHSA-fhhm-9qhh-g52w"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Hyundai infotainment system","requires_auth":"low_privilege","summary":"Attackers can modify the AppDMClient binary to bypass digital signature checks, allowing installation of custom firmware on Hyundai infotainment systems.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gen5w_l_firmware","vendor":"hyundai"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"An issue was discovered in the Hyundai Gen5W_L in-vehicle infotainment system AE_E_PE_EUR.S5W_L001.001.211214. The AppDMClient binary file, which is used during the firmware installation process, can be modified by an attacker to bypass the digital signature check of AppUpgrade and .lge.upgrade.xml files, which are used during the firmware installation process. This indirectly allows an attacker to use a custom version of AppUpgrade and .lge.upgrade.xml files.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2023-26244","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2023-26245"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2023-26243"},"products":["n/a"],"published":"2023-04-27","related":[{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2023-26243","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":7.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-26245","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":7.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-26246","kev_date_added":null,"published":"2023-04-27"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-31","vendors":["n/a"]},"summary":"Attackers can modify the AppDMClient binary to bypass digital signature checks, allowing installation of custom firmware on Hyundai infotainment systems.","url":"https://insights.sbomify.com/CVE-2023-26244/"}