# CVE-2014-0328: Security feature bypass in n/a

> Attackers with physical or terminal access can execute arbitrary code on Cobham devices by bypassing firmware signature verification via SNMP and TFTP.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9pj2-2xqq-q73h

## What is CVE-2014-0328?

CVE-2014-0328 is a critical vulnerability in n/a, published on 15 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The 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.

## Which versions are affected by CVE-2014-0328?

It affects 4 products.


Products: Cobham Ailor 6110 Mini-C Gmdss, Cobham Sailor 6006 Message Terminal, Cobham Sailor 6222 Vhf, Cobham Sailor 6300 Mf \/ Hf.

## How do I fix CVE-2014-0328?

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

## Is CVE-2014-0328 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2941](https://insights.sbomify.com/CVE-2014-2941/): Hardcoded credentials in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0328 and fix it if it is affected.

What it is: CVE-2014-0328 is a critical vulnerability in n/a, published on 15 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0328 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-2014-0328/ (Markdown: https://insights.sbomify.com/CVE-2014-0328/index.md)
```

## Sources

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

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