Local NvRAM modification via misconfigured debug command
Published Aug 11, 2021 · Updated Aug 4, 2024
Improper debug-command configuration in LG mobile devices running Android P or Q allows local users to modify NvRAM content. A debug command is configured to permit writes to NvRAM content that should not be alterable by its low-privilege caller. The flaw requires local access and affects devices using mt6762, mt6765, or mt6883 chipsets, with no reported confidentiality or availability impact.
Summary
What happened
Improper debug-command configuration in LG mobile devices running Android P or Q allows local users to modify NvRAM content. A debug command is configured to permit writes to NvRAM content that should not be alterable by its low-privilege caller. The flaw requires local access and affects devices using mt6762, mt6765, or mt6883 chipsets, with no reported confidentiality or availability impact.
The record
- CVE
- CVE-2021-38591
- Published
- Aug 11, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo