Memory corruption via overflowing NBD option name
Published Mar 6, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in nbd-server before 3.24 allows remote attackers to corrupt memory via a crafted NBD option name. The handle_info and handle_export_name paths add one to the attacker-controlled 32-bit name length, so 0xffffffff wraps the allocation size to zero before a write through the resulting dangling pointer. No authentication or user interaction is required; published evidence establishes server-process memory corruption but no more specific operational outcome.
Summary
What happened
Heap-based buffer overflow in nbd-server before 3.24 allows remote attackers to corrupt memory via a crafted NBD option name. The handle_info and handle_export_name paths add one to the attacker-controlled 32-bit name length, so 0xffffffff wraps the allocation size to zero before a write through the resulting dangling pointer. No authentication or user interaction is required; published evidence establishes server-process memory corruption but no more specific operational outcome.
The record
- CVE
- CVE-2022-26495
- Published
- Mar 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
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
- NBD option-name length proof of conceptproof of concept · unverified
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