CVE-2014-0328
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 · uneditedThe thraneLINK protocol implementation on Cobham devices does not verify firmware signatures, which allows attackers to execute arbitrary code by leveraging physical access or terminal access to send an SNMP request and a TFTP response.
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 confidenceThe thraneLINK protocol implementation on Cobham devices lacks firmware signature verification, allowing attackers with physical or terminal access to inject malicious firmware via SNMP requests and TFTP responses, leading to arbitrary code execution.
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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 the Cobham device modelLocate the device label, web interface, or console output showing the model name. Common locations: physical device label, SNMP sysDescr OID (1.3.6.1.2.1.1.1), or administrative web interface system information page.Affected if The device model matches one of: Cobham Ailor 6110 Mini C Gmdss, Cobham Sailor 6006 Message Terminal, Cobham Sailor 6222 Vhf, or Cobham Sailor 6300 Mf/Hf.
-
Check if firmware signature verification is implementedAccess the device administrative interface (web or console) and navigate to firmware update or security settings. Look for options related to firmware signature validation, cryptographic verification, or secure boot. Query SNMP if available for relevant OIDs.Affected if Firmware signature verification is absent, disabled, or not available as a configuration option in the firmware management settings.
-
Verify SNMP service configurationCheck if SNMP is enabled on the device. Review SNMP community strings, access control lists, and SNMP version in use. Use commands like snmpwalk or check device SNMP configuration pages.Affected if SNMP is enabled with default or weak community strings, or SNMP access is not restricted to trusted management stations.
-
Verify TFTP service configurationCheck if TFTP is enabled for firmware transfers. Review TFTP server settings, access restrictions, and whether firmware can be loaded via TFTP. Inspect device configuration for tftp-related settings.Affected if TFTP is enabled and accessible without authentication, or firmware can be loaded via TFTP without signature validation.
-
Assess physical and terminal access controlsReview physical security measures and console/terminal access restrictions. Check if serial or network-based terminal access is protected by authentication and if physical ports are secured.Affected if Physical console access or terminal interfaces are unprotected, or network-based terminal services allow unauthenticated access.
A user is affected if they operate any of the listed Cobham device models and the device allows firmware loading via SNMP or TFTP without requiring cryptographic signature verification.
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 dataImplement cryptographic signature verification for all firmware before execution and enforce strict access controls on physical and terminal interfaces to prevent unauthorized SNMP/TFTP interactions.
- Consultation4.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0328 — 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-0328 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