CVE-2021-47813
BaseFortify
Publication date: 2026-01-16
Last updated on: 2026-01-16
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nsauditor | backup_key_recovery | 2.2.7 |
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?
CVE-2021-47813 is a denial of service vulnerability in Backup Key Recovery version 2.2.7.0 caused by a buffer overflow. The application does not properly check the size of input when copying data into the registration code input field. An attacker can exploit this by inputting a large buffer of 256 repeated characters into the registration key field, which causes the application to become unstable and crash. [1, 2]
How can this vulnerability impact me? :
This vulnerability can cause the Backup Key Recovery application to crash or become unresponsive, resulting in a denial of service. This means legitimate users may be unable to use the software until it is restarted, potentially disrupting workflows that depend on it. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to reproduce the denial of service condition locally on the affected system. Specifically, you can test the application by launching BackupKeyRecovery.exe, navigating to Register > Enter Registration Code, and pasting a 256-character string (e.g., 256 'A's) into the 'Key' field. If the application crashes or becomes unresponsive, the vulnerability is present. There are no specific network detection commands since the exploit is local and requires user interaction. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding pasting or entering excessively long registration codes (specifically 256 characters) into the application to prevent triggering the buffer overflow. Additionally, restrict user access to the Backup Key Recovery application to trusted users only, and monitor for any application crashes related to registration code input. Applying any available patches or updates from the vendor once released is also recommended. [1, 2]