dbcve.org
Sea Tel Coastal 18 FirmwareOperating system · Cobham

CVE-2019-16320

MEDIUM · 5.3 CVSS v3.1 Published 2019-09-15
Fix available
A fix is available. Upgrade to after 194_225444 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cobham Sea Tel v170 224521 through v194 225444 devices allow attackers to obtain potentially sensitive information, such as a vessel's latitude and longitude, via the public SNMP community.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cobham Sea Tel maritime satellite communication devices (versions v170 224521 through v194 225444) expose an SNMP service with the default 'public' community string, allowing unauthenticated remote attackers to query the device and retrieve sensitive vessel tracking data including GPS coordinates (latitude and longitude).

MitigationChange the default SNMP community strings from 'public' to strong, unique values on all affected devices and restrict SNMP access to authorized management IP addresses via firewall rules or ACLs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sea Tel Coastal 18 FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sailor 600 Vsat Ku FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sailor 800 Vsat FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sailor 900 Vsat FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sailor 900 Vsat High Power FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sea Tel 4009 Vsat Broadband At Sea FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sea Tel 5012 Vsat FirmwareOperating system
Affected:>= 170_224521, <= 194_225444
Sea Tel 6012 Vsat Ku Band FirmwareOperating system
Affected:>= 170_224521, <= 194_225444

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Determine if the target device is a Cobham Sea Tel product such as Coastal 18, Sailor 600 Vsat Ku, Sailor 800 Vsat, Sailor 900 Vsat, Sailor 900 Vsat High Power, Sea Tel 4009 Vsat Broadband At Sea, Sea Tel 5012 Vsat, or Sea Tel 6012 Vsat Ku Band. Consult the device web interface, management console, or physical labeling.
    Affected if The device is one of the listed Cobham Sea Tel models.
  2. Check the firmware version
    Access the device management interface (typically via web UI or CLI) and retrieve the firmware version information. Compare the installed version against the affected range: greater than or equal to 170_224521 and less than or equal to 194_225444.
    Affected if The installed firmware version falls within 170_224521 through 194_225444.
  3. Verify SNMP service is exposed
    Confirm that SNMP (ports 161/UDP or 162/UDP) is listening on the device or accessible from the network. Use a port scanner or test SNMP connectivity with a tool such as snmpwalk from an external host.
    Affected if The SNMP service is accessible from a network location.
  4. Test default community string
    Attempt an SNMP query using the 'public' community string against the device (e.g., snmpwalk -v2c -c public <device_ip>). Successful retrieval of OID values confirms the default string is in use.
    Affected if SNMP queries using the 'public' community string return valid data.
  5. Check for GPS data exposure
    Query SNMP OIDs related to location or GPS data (such as .1.3.6.1.4.1.26100.1 or similar vendor-specific OIDs) using the 'public' community string to verify if sensitive vessel tracking coordinates are accessible.
    Affected if SNMP queries return GPS coordinates, latitude, longitude, or location data.

The environment is affected if the device is a Cobham Sea Tel model running firmware between 170_224521 and 194_225444 with SNMP enabled and the default 'public' community string still configured, allowing unauthenticated access to sensitive vessel tracking data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 194_225444
Interim mitigation

Change the default SNMP community strings from 'public' to strong, unique values on all affected devices and restrict SNMP access to authorized management IP addresses via firewall rules or ACLs.

Fix this in Sea Tel Coastal 18 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-16320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-16320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data