Samsung Mobile Devices Use-After-Free Vulnerability
Exploited since 2023-09-18. No WAF vendor names it yet.
An improper check or handling of exceptional conditions in NPU driver prior to SMR Jan-2022 Release 1 allows arbitrary memory write and code execution.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable with local access under specific conditions, with low privileges and user interaction, leading to low impact on confidentiality, integrity and availability, and the impact can reach components beyond the vulnerable one.
How the score is built
- Attack vectorAn attacker needs local access, or must trick a user into opening something on the machine.Local
- Attack complexityThe attack only works when conditions outside the attacker's control line up.High
- Privileges requiredThe attacker needs an ordinary user account.Low
- User interactionA user has to do something first, such as open a file or click a link.Required
- ScopeThe attack can spread beyond the vulnerable component to other parts of the system.Changed
- Confidentiality impactAn attacker can read some data, but has no control over what they get.Low
- Integrity impactAn attacker can change some data, but with limited control or limited effect.Low
- Availability impactAn attacker can slow the component down or interrupt it now and then.Low
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:LAttackers are exploiting this in the wild.
At least one step needs hands-on work, which slows mass attacks.
A successful attack gives full control over the affected software or all of its data.
Public exploits
None foundNo exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.
Timeline
- 2022-01-07CVE publishedCVE List
- 2023-09-18Added to CISA KEVConfirmed exploitation in the wild
Vendor statements
QuotedCloudflareWAF Managed Rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.