# CVE-2024-26303: Denial of service in ArubaOS-S Switch

> Authenticated attackers can cause a denial of service in the ArubaOS-Switch SSH daemon, requiring network administrators to apply vendor patches.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-vwvv-5f5j-x28v

## What is CVE-2024-26303?

CVE-2024-26303 is a medium-severity denial of service vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS-S Switch, published on 26 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Authenticated Denial of Service Vulnerability in ArubaOS-Switch SSH Daemon

## Which versions are affected by CVE-2024-26303?


## How do I fix CVE-2024-26303?

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

## Is CVE-2024-26303 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26303 and fix it if it is affected.

What it is: CVE-2024-26303 is a medium-severity denial of service vulnerability in Hewlett Packard Enterprise (HPE) ArubaOS-S Switch, published on 26 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26303 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) ArubaOS-S Switch. 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-2024-26303/ (Markdown: https://insights.sbomify.com/CVE-2024-26303/index.md)
```

## Sources

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

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