# CVE-2024-3080: ASUS Router - Improper Authentication

> Unauthenticated remote attackers can bypass authentication to log in to vulnerable ASUS routers, gaining unauthorized access to the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 14 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-6c6m-p94j-g86j

## What is CVE-2024-3080?

CVE-2024-3080 is a critical authentication bypass vulnerability in ASUS RT-AC68U, published on 14 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain ASUS router models have authentication bypass vulnerability, allowing unauthenticated remote attackers to log in the device.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2024-3080 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3080 exists.

Public exploit code:

- ASUS DSL-AC88U - Authentication Bypass (nuclei): http/cves/2024/CVE-2024-3080.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3080 is a critical authentication bypass vulnerability in ASUS RT-AC68U, published on 14 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3080 exists.

Affected product: ASUS RT-AC68U. 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-3080/ (Markdown: https://insights.sbomify.com/CVE-2024-3080/index.md)
```

## Sources

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

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