CVE-2014-2941
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 · uneditedCobham Sailor 6000 satellite terminals have hardcoded Tbus 2 credentials, which allows remote attackers to obtain access via a TBUS2 command. NOTE: the vendor reportedly states "there is no possibility to exploit another user's credentials.
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 · moderate confidenceCobham Sailor 6000 satellite terminals contain hardcoded Tbus 2 credentials embedded in the firmware. Remote attackers can obtain these credentials via TBUS2 commands and use them to gain unauthorized access to the terminal management interface.
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 dataall versionsall versionsall versionsall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Complete
- Availability
- None
AV:N/AC:M/Au:N/C:N/I:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Cobham Sailor terminal modelLocate the device model number on the physical hardware or in the system inventory. Common locations include the device label, management console, or network device discovery.Affected if The model is one of: Sailor 6110 Mini C Gmdss, Sailor 6006 Message Terminal, Sailor 6222 Vhf, or Sailor 6300 MF/HF. All versions of these models are affected.
-
Verify TBUS2 management interface accessibilityDetermine if the TBUS2 interface is reachable on the terminal. This is typically accessed via the terminal's management network port or console. Consult the product documentation for the specific IP address or connection method.Affected if The TBUS2 management interface is accessible over the network, indicating the attack surface exists for remote exploitation.
-
Check if default TBUS2 credentials are in useReview the terminal configuration to determine whether the default TBUS2 credentials (username and password) have been changed from the factory默认值.Affected if The default TBUS2 credentials remain unchanged, meaning the hardcoded credentials from the firmware would grant unauthorized access.
-
Assess network exposure of the management interfaceReview firewall rules, ACLs, and network segmentation to determine if the terminal management interface is accessible from untrusted networks or the public internet.Affected if The TBUS2 management interface is exposed to untrusted networks, allowing remote attackers to obtain and use the hardcoded credentials.
You are affected if you operate any of the listed Cobham Sailor terminal models and the TBUS2 management interface with default credentials is accessible from your network.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace default Tbus 2 credentials with strong, unique passwords; implement network access controls to limit exposure of management interfaces; contact vendor for firmware updates if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2941 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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