{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46139 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46139 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46139 is a medium-severity authentication bypass vulnerability in tiann KernelSU, published on 30 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46139 and fix it if it is affected.\n\nWhat it is: CVE-2023-46139 is a medium-severity authentication bypass vulnerability in tiann KernelSU, published on 30 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-46139 in the wild and no public exploit code.\n\nAffected product: tiann KernelSU. 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-46139/ (Markdown: https://insights.sbomify.com/CVE-2023-46139/index.md)","id":"CVE-2023-46139","markdown":"https://insights.sbomify.com/CVE-2023-46139/index.md","name":"CVE-2023-46139","record":{"aliases":["GHSA-86cp-3prf-pwqq"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android root solution","requires_auth":"low_privilege","summary":"Malicious apps can bypass KernelSU signature checks to gain root privileges on Android devices due to inconsistent verification logic.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kernelsu","vendor":"kernelsu"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"KernelSU is a Kernel based root solution for Android. Starting in version 0.6.1 and prior to version 0.7.0, if a KernelSU installed device is infected with a malware whose app signing block specially constructed, it can take over root privileges on the device. The vulnerable verification logic actually obtains the signature of the last block with an id of `0x7109871a`, while the verification logic during Android installation is to obtain the first one. In addition to the actual signature upgrade that has been fixed (KSU thought it was V2 but was actually V3), there is also the problem of actual signature downgrading (KSU thought it was V2 but was actually V1). Find a condition in the signature verification logic that will cause the signature not to be found error, and KernelSU does not implement the same conditions, so KSU thinks there is a V2 signature, but the APK signature verification actually uses the V1 signature. This issue is fixed in version 0.7.0. As workarounds, keep the KernelSU manager installed and avoid installing unknown apps.","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":"KernelSU signature validation mismatch","id":"CVE-2023-46139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":7,"next":{"headline":"Missing authorization in AXC 1050","id":"CVE-2023-46141"},"packages":[],"prev":{"headline":"JumpServer default admin user email leak password reset","id":"CVE-2023-46138"},"products":["KernelSU"],"published":"2023-10-30","related":[{"cvss_score":7.3,"headline":"Incorrect Authorization in tiann/kernelsu","id":"CVE-2023-5521","kev_date_added":null,"published":"2023-10-11"},{"cvss_score":6.7,"headline":"The logic of get apk path in KernelSU module can be bypassed","id":"CVE-2023-49794","kev_date_added":null,"published":"2024-01-02"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-05","vendors":["tiann"]},"summary":"Malicious apps can bypass KernelSU signature checks to gain root privileges on Android devices due to inconsistent verification logic.","url":"https://insights.sbomify.com/CVE-2023-46139/"}