CVE-2019-25464
Buffer Overflow in InputMapper 1.6.10 Causes Application Crash
Publication date: 2026-03-11
Last updated on: 2026-03-11
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| inputmapper | inputmapper | to 1.6.10 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2019-25464 is a buffer overflow vulnerability in InputMapper version 1.6.10, specifically in the username field.
Local attackers can exploit this by entering an excessively long string into the username field and then double-clicking to process it, which causes the application to crash.
This vulnerability results from improper handling of input length, leading to a denial of service condition.
How can this vulnerability impact me? :
The primary impact of this vulnerability is a denial of service (DoS) condition.
An attacker with local access can cause the InputMapper application to crash by inputting a very long string into the username field and triggering its processing.
This crash disrupts normal application functionality, potentially preventing legitimate users from using the software 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 crash condition locally on the system running InputMapper 1.6.10 or earlier. Specifically, you can test the application by inputting an excessively long string into the username field and observing if the application crashes.'}, {'type': 'paragraph', 'content': 'A practical method is to generate a long string (e.g., 15,000 characters) and paste it into the username field, then double-click the field to trigger processing. If the application crashes, the vulnerability is present.'}, {'type': 'paragraph', 'content': 'For example, you can generate a long string using a simple Python command:'}, {'type': 'list_item', 'content': 'python -c "print(\'A\'*15000)" > exploit.txt'}, {'type': 'paragraph', 'content': 'Then, copy the contents of exploit.txt into the username field in InputMapper and double-click to process it.'}] [3]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, avoid entering excessively long strings into the username field in InputMapper 1.6.10 or earlier versions.
Since the vulnerability requires local access and user interaction, restricting access to trusted users and educating them not to input large payloads can reduce risk.
Additionally, consider updating to a newer version of InputMapper if available, as newer versions may have addressed this issue.