Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2019-2215

HIGH
Published
Oct 11, 2019
Updated
Mar 15, 2026
Affected
0 pkgs
Patched
None yet
Exploits
38 known

EPSS Exploitation Probability

via FIRST.org ↗
51.5%probability of exploitation in next 30 days
High Risk98th percentile0.00%
48.4%50.7%52.9%55.2%51.8%51.5%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel. No user interaction is required to exploit this vulnerability, however exploitation does require either the installation of a malicious local application or a separate vulnerability in a network facing application.Product: AndroidAndroid ID: A-141720095

Exploits & PoCs
38

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47463localandroid✓ Verified

Android - Binder Driver Use-After-Free

by Google Security Research · Oct 4, 2019

EDB-48129localandroid✓ Verified

Android Binder - Use-After-Free (Metasploit)

by Metasploit · Feb 24, 2020

Frequently Asked Questions

A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel. No user interaction is required to exploit this vulnerability, however exploitation does require either the installation of a malicious local application or a separate vulnerability in a network facing application.Product: AndroidAndroid ID: A-141720095
O3 Security · Impact-Aware SCA

Is CVE-2019-2215 in your stack?

O3 detects CVE-2019-2215 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.