# CVE-2014-8428: Privilege escalation in n/a

> Attackers can escalate privileges on Barracuda Load Balancer devices by exploiting an improperly protected SSH key.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 28 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mg9c-8436-cv2g

## What is CVE-2014-8428?

CVE-2014-8428 is a critical vulnerability in n/a, published on 28 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Privilege escalation vulnerability in Barracuda Load Balancer 5.0.0.015 via the use of an improperly protected SSH key.

Weakness: CWE-264

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

It affects 1 product.


Products: Barracuda Load Balancer.

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

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

## Is CVE-2014-8428 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8426](https://insights.sbomify.com/CVE-2014-8426/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8428 is a critical vulnerability in n/a, published on 28 Aug 2017. 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-2014-8428 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-8428/ (Markdown: https://insights.sbomify.com/CVE-2014-8428/index.md)
```

## Sources

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

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