{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7563 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7563 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7563 is a high-severity vulnerability in n/a, published on 7 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-7563 and fix it if it is affected.\n\nWhat it is: CVE-2017-7563 is a high-severity vulnerability in n/a, published on 7 Jun 2017. 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-2017-7563 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-2017-7563/ (Markdown: https://insights.sbomify.com/CVE-2017-7563/index.md)","id":"CVE-2017-7563","markdown":"https://insights.sbomify.com/CVE-2017-7563/index.md","name":"CVE-2017-7563","record":{"aliases":["GHSA-26gw-4gmp-qgf3"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ARM Trusted Firmware","requires_auth":"none","summary":"Attackers can bypass MT_EXECUTE_NEVER protection in ARM Trusted Firmware due to inconsistent execute-never bit handling, compromising secure memory integrity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trusted_firmware-a","vendor":"trustedfirmware"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to bypass the MT_EXECUTE_NEVER protection mechanism. This issue occurs because of inconsistency in the number of execute-never bits (one bit versus two bits).","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-2017-7563","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2017-7564"},"packages":[],"prev":{"headline":"Auth bypass in krb5","id":"CVE-2017-7562"},"products":["n/a"],"published":"2017-06-07","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2017-15031","kev_date_added":null,"published":"2018-12-18"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-7564","kev_date_added":null,"published":"2017-06-07"},{"cvss_score":7.4,"headline":"Information disclosure in n/a","id":"CVE-2022-47630","kev_date_added":null,"published":"2023-01-16"},{"cvss_score":7,"headline":"Integer overflow in n/a","id":"CVE-2017-9607","kev_date_added":null,"published":"2017-09-20"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2018-19440","kev_date_added":null,"published":"2019-01-29"}],"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 MT_EXECUTE_NEVER protection in ARM Trusted Firmware due to inconsistent execute-never bit handling, compromising secure memory integrity.","url":"https://insights.sbomify.com/CVE-2017-7563/"}