Privileged device-state tampering
Published Nov 10, 2021 · Updated Aug 19, 2026
Tampering in Microsoft Azure Sphere before 21.10 allows local users with high privileges to modify protected device state. Microsoft has not published the affected component or the operation that improperly accepts or applies attacker-controlled data. Exploitation requires high local privileges and crosses a security boundary; the documented impact is integrity loss without confidentiality or availability impact.
Summary
What happened
Tampering in Microsoft Azure Sphere before 21.10 allows local users with high privileges to modify protected device state. Microsoft has not published the affected component or the operation that improperly accepts or applies attacker-controlled data. Exploitation requires high local privileges and crosses a security boundary; the documented impact is integrity loss without confidentiality or availability impact.
The record
- CVE
- CVE-2021-42300
- Published
- Nov 10, 2021
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Azure Sphere
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20.00 <22.07
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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