1

CVE-2022-20411 enabled remote code execution over Bluetooth on Android. It was fixed in December 2022. But why was it not detected by Android's BoundsSanitizer? Its purpose is to detect and prevent Out of Bounds array accesses and it is deployed "in Bluetooth and codecs.".

So basically it failed in every regard. How? Why?

Improve this question
4
  • I think CVE-2020-27024 may be interesting since it's also about out-of-bounds read, but also noted that "Bounds Sanitizer mitigates this in the default configuration."
    – Andrew T.
    Jan 27 at 14:29
  • @AndrewT. interesting, indeed! But this confuses me even more. If the BoundsSanitizer mitigates the vulnerability, doesn't that mean that the vulnerability should be, well, mitigated? So why does it exist?
    – Finni
    Feb 2 at 17:05
  • What I understood from the Android Documentation is that Bounds Sanitizer can be configured on or off when building the ROM. So I think the CVE is for general info, especially for ROM makers who disable the check for whatever reason.
    – Andrew T.
    Feb 3 at 1:51
  • @AndrewT. that makes sense. I forgot that every manufacturer builds the code themselves. But still, if the BoundSanitizer found the issue, couldn't Google have fixed it before publishing it?
    – Finni
    Feb 3 at 13:21

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .