Application crash via oversized registration name
Published Feb 5, 2026 · Updated Feb 5, 2026
Classic buffer overflow in Nsasoft NSAuditor 3.2.0.0 allows local users to crash the application via the registration name field. The registration dialog accepts a 1,000-byte repeated-character name and copies it without checking the destination buffer size. Exploitation requires access to the Windows GUI and an active step that pastes the payload and confirms the registration dialog; the demonstrated consequence is an application crash.
Summary
What happened
Classic buffer overflow in Nsasoft NSAuditor 3.2.0.0 allows local users to crash the application via the registration name field. The registration dialog accepts a 1,000-byte repeated-character name and copies it without checking the destination buffer size. Exploitation requires access to the Windows GUI and an active step that pastes the payload and confirms the registration dialog; the demonstrated consequence is an application crash.
The record
- CVE
- CVE-2020-37130
- Published
- Feb 5, 2026
- Updated
- Feb 5, 2026
- Vendor
- Nsasoft
- Product
- NSAuditor
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2026CVE publishedPublication date reported by the CVE source.
- Feb 5, 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=3.2.0.0
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
Public exploit references
- Nsauditor 3.2.0.0 - 'Name' Denial of Service (PoC)proof of concept · demonstrated
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