@corbet just another lap in the crazy CVE merry-go-round. It's so bad it's even hard to giggle at it.
@corbet I’m surprised people give forbes the time of day, after the supermicro thing that went nowhere.
@corbet I think you're right in your assessment. UVC video is nothing that would be easily exploitable remotely or something.
It *is* a risk for anyone plugging in devices at untrusted places and just accepts any USB connections, which is restricted heavily in modern-ish Android versions and requires user interaction and an unlocked screen in most cases.
@jonas
one needs to look at actual CVSS codes to know the details, e.g. "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" in this case. To view it in human readable form use e.g.: https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Or you learn the codes by heart with time - AV:L in particular means "attack vector: local". It is not marked as "av:p(hysical)" though, so it would imply it can be exploited by locally installed malicious app without the need for physical access (e.g. plugging in malicious device)