Missing AuthenticationWeakness · CWE-306

CVE-2024-57725

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Arcadyan Livebox Fibra PRV3399B_B_LT router has an authentication bypass vulnerability in the /firstconnection.cgi endpoint. An unauthenticated remote or local attacker can modify GPON link configuration values, causing internet service disruption.

MitigationApply vendor firmware update when available. Until then, restrict network access to management interfaces via firewall rules or network segmentation, and monitor for unauthorized configuration changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model
    Access the router's web interface or check the device label to verify the model number is Arcadyan Livebox Fibra PRV3399B_B_LT
    Affected if The device model matches PRV3399B_B_LT and the firmware has not been patched
  2. Check firmware version
    Log into the router admin panel and navigate to the status or system information page to view the installed firmware version
    Affected if The firmware version is older than the vendor patch (if known) or remains at the original vulnerable version
  3. Verify endpoint accessibility
    Attempt to access http://<router-ip>/firstconnection.cgi from an unauthenticated browser session
    Affected if The endpoint loads or responds without requiring login credentials, indicating the authentication bypass is present
  4. Check GPON configuration integrity
    Log into the router admin panel and navigate to the GPON or WAN settings to review the current link configuration values (OLT ID, ONU ID, optical power settings)
    Affected if GPON parameters have been altered unexpectedly or differ from your known-good baseline configuration
  5. Audit access logs for endpoint hits
    Review router logs or firewall logs for any requests to /firstconnection.cgi from unauthorized IP addresses
    Affected if Logs show unauthenticated access to the firstconnection.cgi endpoint from unexpected sources

If the device is an Arcadyan Livebox Fibra PRV3399B_B_LT with unpatched firmware and the /firstconnection.cgi endpoint is accessible without authentication, the device is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update when available. Until then, restrict network access to management interfaces via firewall rules or network segmentation, and monitor for unauthorized configuration changes.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57725 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data