CVE-2020-37199
Denial of Service via Buffer Overflow in NBMonitor
Publication date: 2026-02-11
Last updated on: 2026-02-26
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nsasoft | nbmonitor | to 1.6.6.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2020-37199 is a denial of service (DoS) vulnerability in NBMonitor version 1.6.6.0 and earlier. It occurs in the application's registration key input field, where an attacker can input a specially crafted payload of 1000 characters into the 'Key' field. This causes the application to crash due to improper handling of the input size, classified under CWE-120 (Buffer Copy without Checking Size of Input)."}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by causing the NBMonitor application to crash when a maliciously crafted 1000-character payload is entered into the registration key field. This results in a denial of service condition, making the application unavailable or unstable until it is restarted.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by attempting to reproduce the denial of service condition on the NBMonitor application version 1.6.6.0 or earlier.'}, {'type': 'paragraph', 'content': 'A proof-of-concept method involves generating a payload of 1000 characters (e.g., 1000 "A" characters) and pasting it into the \'Key\' field of the NBMonitor registration dialog to see if the application crashes.'}, {'type': 'paragraph', 'content': 'A sample command to generate the payload file using Python is:'}, {'type': 'list_item', 'content': 'python -c "print(\'A\'*1000)" > poc.txt'}, {'type': 'paragraph', 'content': "Then, open NBMonitor, go to the registration key input, paste the contents of poc.txt into the 'Key' field, and submit to check if the application crashes, indicating the vulnerability."}] [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding pasting or entering excessively long or malformed registration keys (such as 1000-character inputs) into the NBMonitor application.
Since the vulnerability requires user interaction and local access, restricting access to the application and educating users to not input suspicious or overly long keys can reduce risk.
Additionally, monitoring for application crashes related to the registration key input can help detect exploitation attempts.
Ultimately, updating to a fixed or newer version of NBMonitor (if available) or contacting the vendor for patches is recommended.