LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25252: FTP Voyager 16.2.0 Denial of Service via Malformed Site Profile

FTP Voyager 16.2.0 contains a denial of service vulnerability that allows local attackers to crash the application by injecting oversized buffer data into the site profile IP field. Attackers can create a malicious site profile containing 500 bytes of repeated characters and paste it into the IP field to trigger a buffer overflow that crashes the FTP Voyager process.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25252 affects FTP Voyager 16.2.0. A malformed saved site profile can crash the FTP Voyager application by overflowing the IP field. This is a local denial-of-service issue against the client application, not evidence of remote compromise of an FTP server.

Executive priority

Treat as a moderate endpoint availability issue. Prioritize if FTP Voyager 16.2.0 is used on operationally important workstations or by teams relying on FTP transfers. It is lower urgency than remotely exploitable server flaws.

Technical view

The issue is reported as CWE-787 out-of-bounds write in FTP Voyager 16.2.0. The CVSS 4.0 vector is local, low complexity, no privileges, no user interaction, with high vulnerable-system availability impact. Public references include ExploitDB and VulnCheck, but the sources do not show CISA KEV listing or active exploitation.

Likely exposure

Exposure is likely limited to endpoints where Serv-U FTP Voyager 16.2.0 is installed and site profiles can be created or modified locally. Server-side Serv-U products are not identified as affected in the provided sources.

Exploitation context

The cited material describes a local application crash using malformed site profile data. A public ExploitDB reference exists, but the provided sources do not establish real-world exploitation or a remote attack path.

Researcher notes

Evidence is narrow and version-specific. The source bundle names FTP Voyager 16.2.0 only. No patch version is provided in the supplied sources. Avoid broad conclusions about other Serv-U products without additional vendor confirmation.

Mitigation direction

  • Identify endpoints running FTP Voyager 16.2.0.
  • Check Serv-U guidance for fixed versions or vendor-recommended mitigation.
  • Avoid importing or using untrusted FTP Voyager site profiles.
  • Limit local access to systems running the affected client.
  • Consider removing the application where it is no longer required.

Validation and detection

  • Inventory installed FTP Voyager versions across managed endpoints.
  • Confirm whether version 16.2.0 is present.
  • Review software management records for vendor updates or replacement.
  • Check whether users handle externally supplied site profiles.
  • Monitor endpoint crash reports for repeated FTP Voyager failures.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-787: 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 lookup
cve · low confidence lookup

CVE-2018-25252 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2018-25252Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Serv-UFTP Voyager16.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.