# CVE-2018-5493: Denial of service in ATTO FibreBridge 7500N

> Unauthenticated remote attackers can cause a Denial of Service on ATTO FibreBridge 7500N devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 7 May 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qjff-6hhq-wmw2

## What is CVE-2018-5493?

CVE-2018-5493 is a high-severity denial of service vulnerability in ATTO FibreBridge 7500N, published on 7 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ATTO FibreBridge 7500N firmware versions prior to 2.90 are susceptible to a vulnerability which allows an unauthenticated remote attacker to cause Denial of Service (DoS).

## Which versions are affected by CVE-2018-5493?

It affects 1 product.


Products: Atto Fibrebridge 7500n Firmware.

## How do I fix CVE-2018-5493?

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

## Is CVE-2018-5493 being exploited?

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

## Other vulnerabilities in ATTO FibreBridge 7500N

- [CVE-2018-5499](https://insights.sbomify.com/CVE-2018-5499/): Denial of service in ATTO FibreBridge 7500N (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5493 and fix it if it is affected.

What it is: CVE-2018-5493 is a high-severity denial of service vulnerability in ATTO FibreBridge 7500N, published on 7 May 2020. 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-2018-5493 in the wild and no public exploit code.

Affected product: ATTO FibreBridge 7500N. 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-2018-5493/ (Markdown: https://insights.sbomify.com/CVE-2018-5493/index.md)
```

## Sources

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

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