Local security-boundary bypass via unsanitized kernel parameters
Published Jun 9, 2020 · Updated Aug 4, 2024
Security feature bypass in affected Microsoft Windows releases allows local users to cross an unspecified kernel security boundary. The Windows Kernel inadequately sanitizes unspecified parameters supplied by a specially crafted application; Microsoft has not identified the affected interface or operation. A locally authenticated attacker must run the application on the target, and the public record does not specify what access or action the bypass grants.
Summary
What happened
Security feature bypass in affected Microsoft Windows releases allows local users to cross an unspecified kernel security boundary. The Windows Kernel inadequately sanitizes unspecified parameters supplied by a specially crafted application; Microsoft has not identified the affected interface or operation. A locally authenticated attacker must run the application on the target, and the public record does not specify what access or action the bypass grants.
The record
- CVE
- CVE-2020-1241
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2020CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified
What conditions does exploitation require?
What is affected?
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