LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19393: Cobham Satcom Sailor 800 and 900 devices contained a vulnerability that allowed for arbitrary writing of co...

Cobham Satcom Sailor 800 and 900 devices contained a vulnerability that allowed for arbitrary writing of content to the system's configuration file. This was exploitable via multiple attack vectors depending on the device's configuration. Further analysis also indicated this vulnerability could be leveraged to achieve a Denial of Service (DoS) condition, where the device would require a factory reset to return to normal operation.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-19393 affects Cobham Satcom Sailor 800 and 900 devices. The reported issue could let an attacker write arbitrary content into the device configuration file and may cause a denial-of-service state requiring a factory reset. Published severity, CVSS, and vendor fix details are not provided in the source bundle.

Executive priority

Prioritize exposed maritime satcom deployments because a successful attack could disrupt communications and require hands-on recovery. Treat internal-only or unreachable devices as lower urgency until exposure is confirmed.

Technical view

The CVE description states arbitrary configuration-file write on Cobham Satcom Sailor 800/900 devices, reachable through multiple vectors depending on device configuration. Further analysis indicated the flaw could be used to trigger a DoS condition. The bundle does not identify specific firmware versions, CWE mapping, CVSS metrics, authentication requirements, or patch status.

Likely exposure

Exposure is most likely where Sailor 800 or 900 systems are deployed and reachable through management or service interfaces. The source bundle does not define affected versions or exact configurations, so asset confirmation is required before scoping risk.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source in the bundle confirms active exploitation. Exploitability depends on device configuration and attack vector availability, but the details are incomplete.

Researcher notes

The public bundle is sparse: no CVSS, CWE, affected version range, authentication details, or vendor remediation are included. Analysis should focus on asset discovery, exposed interfaces, configuration review, and obtaining vendor-specific guidance.

Mitigation direction

  • Inventory Sailor 800 and 900 devices and record firmware versions.
  • Check Cobham Satcom vendor guidance for supported firmware or configuration fixes.
  • Restrict device management interfaces to trusted administrative networks only.
  • Back up approved configurations where operationally appropriate.
  • Plan factory-reset recovery procedures for affected operational environments.

Validation and detection

  • Confirm whether Sailor 800 or 900 devices exist in the environment.
  • Identify which device interfaces are reachable from untrusted networks.
  • Review configuration integrity and recent unauthorized changes.
  • Check vendor advisories or support channels for version-specific remediation.
  • Validate recovery procedures without disrupting production communications.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2018-19393 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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