CVE-2018-25285
Buffer Overflow in Fathom 2.4 Authorization Code Causes DoS
Publication date: 2026-04-26
Last updated on: 2026-04-26
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
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a buffer overflow triggered by submitting an oversized input string (around 6000 bytes) into the Authorization Code field of the Fathom 2.4 application. Detection would involve monitoring for unusually large input submissions to this field or application crashes related to such inputs.
Since the vulnerability is local and triggered by user input within the application, network-based detection commands are not applicable. Instead, detection can be done by testing the application locally with input validation or by monitoring application logs for crashes after large inputs.
No specific commands are provided in the available information.
Can you explain this vulnerability to me?
This vulnerability exists in Fathom 2.4 and is a buffer overflow issue in the Authorization Code field. It allows local attackers to crash the application by submitting an input string that is too large. Specifically, an attacker can paste a 6000-byte payload into the Authorization Code field and activate it, which triggers 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 application to crash by submitting an oversized input to the Authorization Code field, potentially disrupting normal operations and availability of the application.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include preventing users from submitting oversized input strings to the Authorization Code field in the Fathom 2.4 application.
Applying input validation to limit the size of the Authorization Code field input can help avoid triggering the buffer overflow.
Additionally, restricting access to the application to trusted users only, since the vulnerability requires local interaction, can reduce risk.
No patches or updates are mentioned in the provided information.