Cobham Satcom Sailor 800 Firmware
Approved changes feed: RSS · Atom
cpe:2.3:o:cobham:satcom_sailor_800_firmware:-:*:*:*:*:*:*:*
part: o version: - update: *
| Vendor | Cobham (512d488f-9e86-55c1-97a5-a68c12c2142b) |
|---|---|
| Product | Satcom Sailor 800 Firmware (32cfe6b6-76ba-5ddc-8e0f-a624698c0efd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-19394 |
vulnerable | 2026-06-03 14:38:29.262634 |
Details available
Cobham Satcom Sailor 800 and 900 devices contained persistent XSS, which required administrative access to exploit. The vulnerability was exploitable by acquiring a copy of the device's configuration file, inserting an XSS payload into a relevant field (e.g., Satellite name), and then restoring the malicious configuration file.
Published: 2019-03-15T16:00:00.000Z
Updated: 2024-08-05T11:37:11.067Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-19393 |
vulnerable | 2026-06-03 14:38:29.259423 |
Details available
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.
Published: 2019-03-15T16:00:00.000Z
Updated: 2024-08-05T11:37:10.744Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.