# CVE-2009-3836: ArubaOS 3.3.1.x, 3.3.2.x, RN 3.1.x, 3.4.x, and 3.3.2.x-FIPS on the Aruba Mobility Controller allows remote attackers to cause a denial of se


- **Severity:** Medium 6.1 (`AV:A/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-733c-2g2c-8c93

## What is CVE-2009-3836?

CVE-2009-3836 is a medium-severity vulnerability in Arubanetworks Arubaos, published on 2 Nov 2009. 

### Official description

ArubaOS 3.3.1.x, 3.3.2.x, RN 3.1.x, 3.4.x, and 3.3.2.x-FIPS on the Aruba Mobility Controller allows remote attackers to cause a denial of service (Access Point crash) via a malformed 802.11 Association Request management frame.

## Which versions are affected by CVE-2009-3836?

It affects 2 products.


Products: Arubanetworks Aruba Mobility Controller, Arubanetworks Arubaos.

## How do I fix CVE-2009-3836?

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

## Is CVE-2009-3836 being exploited?

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

## Other vulnerabilities in Arubanetworks Arubaos

- [CVE-2008-7023](https://insights.sbomify.com/CVE-2008-7023/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2008-7095](https://insights.sbomify.com/CVE-2008-7095/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3836 and fix it if it is affected.

What it is: CVE-2009-3836 is a medium-severity vulnerability in Arubanetworks Arubaos, published on 2 Nov 2009. 
Exploitation: There is no known exploitation of CVE-2009-3836 in the wild and no public exploit code.

Affected product: Arubanetworks Arubaos. 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-2009-3836/ (Markdown: https://insights.sbomify.com/CVE-2009-3836/index.md)
```

## Sources

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

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