CVE-2020-37180
BaseFortify
Publication date: 2026-02-11
Last updated on: 2026-02-12
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
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-37180 is a denial of service (DoS) vulnerability in GTalk Password Finder version 2.2.1 and earlier. It occurs when an attacker inputs an oversized registration key—specifically a payload of about 1000 characters—into the 'Key' field of the application. This causes the application to crash due to a buffer overflow issue, classified under CWE-120 (Buffer Copy without Checking Size of Input). The attack requires local access and user interaction to trigger the crash."}] [1]
How can this vulnerability impact me? :
This vulnerability can impact you by causing the GTalk Password Finder application to crash when an attacker supplies an oversized registration key. This results in a denial of service, making the application unavailable or unstable. Since the attack requires local access and user interaction, it may disrupt normal use of the software but does not allow for remote exploitation or data compromise.
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 GTalk Password Finder 2.2.1 application. Specifically, an oversized registration key payload of approximately 1000 characters can be generated and input into the 'Key' field of the application to see if it crashes."}, {'type': 'paragraph', 'content': "A practical method involves creating a payload file with 1000 'A' characters using a simple Python script, then pasting this payload into the 'Key' field of the software's registration dialog to observe if the application crashes."}, {'type': 'paragraph', 'content': 'Example command to generate the payload file (poc.txt):'}, {'type': 'list_item', 'content': 'python -c "print(\'A\' * 1000)" > poc.txt'}, {'type': 'paragraph', 'content': "After generating the payload, open GTalk Password Finder 2.2.1, navigate to the registration dialog, paste the contents of poc.txt into the 'Key' field, and click 'Ok'. If the application crashes, the vulnerability is present."}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, avoid using GTalk Password Finder version 2.2.1 or earlier until a patch or update addressing the issue is available.
Since the vulnerability requires local user interaction to trigger the crash, restricting access to the application and limiting user permissions can reduce the risk.
Additionally, monitor for any suspicious activity involving attempts to input oversized registration keys and educate users not to paste or enter unusually long keys.