# CVE-2024-11494: Auth bypass in P-6101C firmware

> Unauthenticated attackers can read device information via crafted HTTP requests on unsupported Zyxel ADSL modems.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2024
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-hffh-x89x-2h44

## What is CVE-2024-11494?

CVE-2024-11494 is a high-severity authentication bypass vulnerability in Zyxel P-6101C firmware, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

**UNSUPPORTED WHEN ASSIGNED** The improper authentication vulnerability in the Zyxel P-6101C ADSL modem firmware version P-6101CSA6AP_20140331 could allow an unauthenticated attacker to read some device information via a crafted HTTP HEAD method.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Zyxel P6101c Firmware.

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

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

## Is CVE-2024-11494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11494 is a high-severity authentication bypass vulnerability in Zyxel P-6101C firmware, published on 20 Nov 2024. 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-2024-11494 in the wild and no public exploit code.

Affected product: Zyxel P-6101C firmware. 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-11494/ (Markdown: https://insights.sbomify.com/CVE-2024-11494/index.md)
```

## Sources

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

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