# CVE-2024-37380: Misconfiguration in UniFi U6+ Access Point

> Incorrect VLAN traffic forwarding in UniFi U6+ Access Points allows attackers to intercept or access traffic from meshed devices.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 22 Jul 2024
- **Updated:** 5 Nov 2024
- **Also known as:** GHSA-r327-g4pc-7fww

## What is CVE-2024-37380?

CVE-2024-37380 is a medium-severity vulnerability in Ubiquiti UniFi U6+ Access Point, published on 22 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A misconfiguration on UniFi U6+ Access Point could cause an incorrect VLAN traffic forwarding to APs meshed to UniFi U6+ Access Point.

Affected Products:
UniFi U6+ Access Point (Version 6.6.65 and earlier) 

 
Mitigation:
Update your UniFi U6+ Access Point to Version 6.6.74 or later.

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


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

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

## Is CVE-2024-37380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37380 is a medium-severity vulnerability in Ubiquiti UniFi U6+ Access Point, published on 22 Jul 2024. 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-2024-37380 in the wild and no public exploit code.

Affected product: Ubiquiti UniFi U6+ Access Point. 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-37380/ (Markdown: https://insights.sbomify.com/CVE-2024-37380/index.md)
```

## Sources

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

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