Security readout for executives and security teams
Plain-English summary
Fathom 2.4 has a local denial-of-service issue in the Authorization Code activation field. A user with access to the application UI can enter an overly long authorization code and trigger an application crash. The available bundle does not show evidence of active exploitation or a confirmed vendor patch.
Executive priority
Treat as a moderate-priority endpoint stability issue. Prioritize shared workstations, lab machines, kiosk-like systems, or environments where untrusted local users can interact with Fathom 2.4.
Technical view
CVE-2018-25285 is a CWE-120 buffer overflow in Fathom 2.4 affecting the Authorization Code field. The CVSS v4.0 score is 6.8 with local attack vector, low complexity, no privileges required, user interaction present, and high impact to vulnerable-system availability only. Confidentiality and integrity impacts are not indicated in the source bundle.
Likely exposure
Exposure is likely limited to systems where Fathom 2.4 is installed and reachable by local or interactive users who can access the activation workflow. This is not described as a remotely exploitable network service issue in the provided sources.
Exploitation context
A public ExploitDB reference exists, so exploit details are publicly available. However, the source bundle marks KEV as false and does not provide evidence of active exploitation in the wild. The supported impact is local application crash/denial of service, not data theft or code execution.
Researcher notes
The bundle identifies Fathom 2.4 only. No other versions, products, CPEs, active exploitation evidence, or confirmed remediation details are provided. Patch status should be verified with the vendor rather than inferred from the existence of product download pages.
Mitigation direction
- Inventory environments for Fathom 2.4 installations and prioritize systems used by untrusted or shared local users.
- Check official Fathom/Concord download or vendor guidance for a fixed or newer supported release before assuming a patch exists.
- Restrict access to the application and activation workflow to trusted users until vendor guidance or an upgrade path is confirmed.
- Monitor endpoint crash reports and helpdesk reports for repeated Fathom activation failures or unexpected application termination.
- If no vendor fix is available and the application is not business-critical, consider removing or isolating Fathom 2.4 from shared workstations.
Validation and detection
- Confirm whether Fathom 2.4 is installed in software inventory or endpoint management records.
- Verify who can launch the application and access the Authorization Code activation UI on affected machines.
- Review vendor/download information for a newer supported version or advisory that addresses this issue.
- Confirm endpoint monitoring captures Fathom application crashes so attempted denial-of-service activity can be detected.
- For organizations maintaining wrappers, packaging, or controls around the application, validate that untrusted users cannot reach the vulnerable activation path.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-25285 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-45294CVE reference · exploit
- Official Product HomepageCVE reference · product
- Product ReferenceCVE reference · product
- VulnCheck Advisory: Fathom 2.4 Denial of Service via Authorization Code Buffer OverflowCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.