# CVE-2024-57725: Missing authorization in n/a

> Remote attackers can modify GPON link values without authentication, causing internet service disruption on Arcadyan Livebox Fibra devices.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 14 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-8qxw-vh64-m92m

## What is CVE-2024-57725?

CVE-2024-57725 is a medium-severity missing authorization vulnerability in n/a, published on 14 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in the Arcadyan Livebox Fibra PRV3399B_B_LT allows a remote or local attacker to modify the GPON link value without authentication, causing an internet service disruption via the /firstconnection.cgi endpoint.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2024-57725 being exploited?

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

Public exploit code:

- This repository documents an unauthenticated GPON manipulation vulnerability discovered in certain Arcadyan routers. (github_poc): https://github.com/pointedsec/CVE-2024-57725

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57725 is a medium-severity missing authorization vulnerability in n/a, published on 14 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57725 exists.

Affected product: n/a. 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-57725/ (Markdown: https://insights.sbomify.com/CVE-2024-57725/index.md)
```

## Sources

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

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