{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-24658 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24658 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24658 is a high-severity vulnerability in n/a, published on 24 Dec 2020. 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-2020-24658 and fix it if it is affected.\n\nWhat it is: CVE-2020-24658 is a high-severity vulnerability in n/a, published on 24 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-24658 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-2020-24658/ (Markdown: https://insights.sbomify.com/CVE-2020-24658/index.md)","id":"CVE-2020-24658","markdown":"https://insights.sbomify.com/CVE-2020-24658/index.md","name":"CVE-2020-24658","record":{"aliases":["GHSA-w56g-cw97-958x"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Arm Compiler 5","requires_auth":"low_privilege","summary":"Arm Compiler 5 stack protection fails to detect corruption if both guard and reference values are overwritten, bypassing security checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"arm_compiler","vendor":"arm"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","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-787","name":"Out-of-bounds Write"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Arm Compiler 5 through 5.06u6 has an error in a stack protection feature designed to help spot stack-based buffer overflows in local arrays. When this feature is enabled, a protected function writes a guard value to the stack prior to (above) any vulnerable arrays in the stack. The guard value is checked for corruption on function return; corruption leads to an error-handler call. In certain circumstances, the reference value that is compared against the guard value is itself also written to the stack (after any vulnerable arrays). The reference value is written to the stack when the function runs out of registers to use for other temporary data. If both the reference value and the guard value are written to the stack, then the stack protection will fail to spot corruption when both values are overwritten with the same value. For both the reference value and the guard value to be corrupted, there would need to be both a buffer overflow and a buffer underflow in the vulnerable arrays (or some other vulnerability that causes two separated stack entries to be corrupted).","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-2020-24658","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"An issue was discovered in GnuTLS before 3.6.15.","id":"CVE-2020-24659"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2020-24656"},"products":["n/a"],"published":"2020-12-24","related":[{"cvss_score":7.8,"headline":"Insecure directory permissions on installer files","id":"CVE-2022-43701","kev_date_added":null,"published":"2023-07-27"},{"cvss_score":7.8,"headline":"Incomplete verification of installation file signature","id":"CVE-2022-43702","kev_date_added":null,"published":"2023-07-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Arm Compiler 5 stack protection fails to detect corruption if both guard and reference values are overwritten, bypassing security checks.","url":"https://insights.sbomify.com/CVE-2020-24658/"}