{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38155 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-38155 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-38155 is a high-severity denial of service vulnerability in n/a, published on 11 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-38155 and fix it if it is affected.\n\nWhat it is: CVE-2022-38155 is a high-severity denial of service vulnerability in n/a, published on 11 Aug 2022. 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-2022-38155 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-2022-38155/ (Markdown: https://insights.sbomify.com/CVE-2022-38155/index.md)","id":"CVE-2022-38155","markdown":"https://insights.sbomify.com/CVE-2022-38155/index.md","name":"CVE-2022-38155","record":{"aliases":["GHSA-q48p-hrg2-rjmf"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung mTower TEE","requires_auth":"none","summary":"A trusted application can cause a kernel crash in Samsung mTower TEE by triggering excessive memory allocation via a large length value.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mtower","vendor":"samsung"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"TEE_Malloc in Samsung mTower through 0.3.0 allows a trusted application to achieve Excessive Memory Allocation via a large len value, as demonstrated by a Numaker-PFM-M2351 TEE kernel crash.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2022-38155","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2022-38156"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2022-38153"},"products":["n/a"],"published":"2022-08-11","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2022-35858","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-40757","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-40758","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2022-40759","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-40760","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-40761","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-40762","kev_date_added":null,"published":"2022-09-16"}],"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-03","vendors":["n/a"]},"summary":"A trusted application can cause a kernel crash in Samsung mTower TEE by triggering excessive memory allocation via a large length value.","url":"https://insights.sbomify.com/CVE-2022-38155/"}