{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15543 exists.","fix":"No fix has been published for CVE-2018-15543 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15543 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Oct 2018. 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-2018-15543 and fix it if it is affected.\n\nWhat it is: CVE-2018-15543 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Oct 2018. 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-2018-15543 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-2018-15543/ (Markdown: https://insights.sbomify.com/CVE-2018-15543/index.md)","id":"CVE-2018-15543","markdown":"https://insights.sbomify.com/CVE-2018-15543/index.md","name":"CVE-2018-15543","record":{"aliases":["GHSA-4cfw-g6m2-82xj"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Telegram Android app","requires_auth":"none","summary":"Attackers can bypass biometric authentication in the Telegram Android app by manipulating callback methods, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram","vendor":"telegram"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An issue was discovered in the org.telegram.messenger application 4.8.11 for Android. The FingerprintManager class for Biometric validation allows authentication bypass through the callback method from onAuthenticationFailed to onAuthenticationSucceeded with null, because the fingerprint API in conjunction with the Android keyGenerator class is not implemented. In other words, an attacker could authenticate with an arbitrary fingerprint.  NOTE: the vendor indicates that this is not an attack of interest within the context of their threat model, which excludes Android devices on which rooting has occurred","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":"Auth bypass in n/a","id":"CVE-2018-15543","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-15546"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2018-15542"},"products":["n/a"],"published":"2018-10-09","related":[{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2019-10044","kev_date_added":null,"published":"2019-03-25"},{"cvss_score":8.1,"headline":"Server-side request forgery in n/a","id":"CVE-2018-20436","kev_date_added":null,"published":"2018-12-24"},{"cvss_score":7.1,"headline":"Improper multimedia file attachment validation in Telegram for Android app","id":"CVE-2024-7014","kev_date_added":null,"published":"2024-07-23"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2021-31320","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2021-31321","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2020-12474","kev_date_added":null,"published":"2020-05-01"}],"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":"2024-11-14","vendors":["n/a"]},"summary":"Attackers can bypass biometric authentication in the Telegram Android app by manipulating callback methods, allowing unauthorized access.","url":"https://insights.sbomify.com/CVE-2018-15543/"}