# CVE-2025-24846: Auth bypass in FutureNet AS-210/U4

> Remote unauthenticated attackers can bypass authentication to obtain device information like MAC addresses on FutureNet AS series industrial routers.

- **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:** 3 Mar 2025
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-xjhw-gq27-xgjr

## What is CVE-2025-24846?

CVE-2025-24846 is a high-severity authentication bypass vulnerability in Century Systems Co., Ltd. FutureNet AS-210/U4, published on 3 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass vulnerability exists in FutureNet AS series (Industrial Routers) provided by Century Systems Co., Ltd. If this vulnerability is exploited, a remote unauthenticated attacker may obtain the device information such as MAC address by sending a specially crafted request.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-24846?


## How do I fix CVE-2025-24846?

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

## Is CVE-2025-24846 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24846 and fix it if it is affected.

What it is: CVE-2025-24846 is a high-severity authentication bypass vulnerability in Century Systems Co., Ltd. FutureNet AS-210/U4, published on 3 Mar 2025. 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-2025-24846 in the wild and no public exploit code.

Affected product: Century Systems Co., Ltd. FutureNet AS-210/U4. 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-2025-24846/ (Markdown: https://insights.sbomify.com/CVE-2025-24846/index.md)
```

## Sources

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

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