# CVE-2018-19393: Missing authorization in n/a

> Attackers can arbitrarily write to configuration files and cause denial of service on Cobham Satcom Sailor devices, requiring factory reset.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fvr7-9mcc-7r67

## What is CVE-2018-19393?

CVE-2018-19393 is a high-severity missing authorization vulnerability in n/a, published on 15 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-19393?

It affects 2 products.


Products: Cobham Satcom Sailor 800 Firmware, Cobham Satcom Sailor 900 Firmware.

## How do I fix CVE-2018-19393?

No fix has been published for CVE-2018-19393 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-19393 being exploited?

There is no known exploitation of CVE-2018-19393 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-19394](https://insights.sbomify.com/CVE-2018-19394/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-19393 and fix it if it is affected.

What it is: CVE-2018-19393 is a high-severity missing authorization vulnerability in n/a, published on 15 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19393 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-19393/ (Markdown: https://insights.sbomify.com/CVE-2018-19393/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-19393
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-19393
- OSV: https://osv.dev/vulnerability/CVE-2018-19393

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-19393/
Summaries are generated and may contain mistakes; the official description above is the record.