SYSTEM code execution via NFSv4 response overflow
Published Jun 15, 2022 · Updated Jan 2, 2025
Buffer overflow in Windows NFS on Windows Server 2012 through 2019 allows remote attackers to execute code as SYSTEM via NFSv4.1 requests. Nfs4SvrXdrpGetEncodeOperationResultByteCount omits each opcode's four bytes when sizing a compound-response buffer, so 19 or more operations overflow the allocation. Server for NFS must be enabled with NFSv4.1; unsuccessful exploitation can crash the host rather than execute code.
Summary
What happened
Buffer overflow in Windows NFS on Windows Server 2012 through 2019 allows remote attackers to execute code as SYSTEM via NFSv4.1 requests. Nfs4SvrXdrpGetEncodeOperationResultByteCount omits each opcode's four bytes when sizing a compound-response buffer, so 19 or more operations overflow the allocation. Server for NFS must be enabled with NFSv4.1; unsuccessful exploitation can crash the host rather than execute code.
The record
- CVE
- CVE-2022-30136
- Published
- Jun 15, 2022
- Updated
- Jan 2, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Jan 2, 2025Record 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=10.0.17763.0 <10.0.17763.3046
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
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