CVE-2020-24376
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 · uneditedA DNS rebinding vulnerability in the UPnP IGD implementations in Freebox v5 before 1.5.29 and Freebox Server before 4.2.3.
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 confidenceA DNS rebinding vulnerability in the UPnP IGD (Internet Gateway Device) implementations of Freebox routers allows attackers to bypass same-origin policies and manipulate port mappings by controlling DNS resolution timing. This enables unauthorized access to internal network services through the UPnP interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.2.3< 4.2.3< 4.2.3< 4.2.3< 4.2.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Freebox router modelLog into the Freebox admin interface (usually at freebox.free.fr or 192.168.1.1) and check the device model under Settings > Freebox > Overview, or look at the physical device labelAffected if The device is a Freebox Revolution, Mini, One, Delta, or Pop model
-
Check installed firmware versionIn the Freebox admin interface, navigate to Settings > Freebox > Overview to view the current firmware version numberAffected if Firmware version is below 4.2.3 (for any of the affected models)
-
Verify UPnP IGD statusIn the Freebox admin interface, go to Settings > Network > UPnP / IGD and check if UPnP IGD is enabledAffected if UPnP IGD is turned ON and the device has not been patched to firmware 4.2.3 or later
You are affected if you own a Freebox router (Revolution, Mini, One, Delta, or Pop) running firmware version below 4.2.3 with UPnP IGD functionality enabled.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped4.2.3
Update Freebox v5 to firmware 1.5.29 or later, and Freebox Server to firmware 4.2.3 or later, to patch the vulnerable UPnP IGD implementation.
Freebox Server Firmware 4.2.3 (or Freebox v5 firmware 1.5.29 if applicable)
- Access the Freebox web interface at mafreebox.freebox.fr
- Log in with your admin credentials
- Navigate to Settings > System > Firmware Update
- Check the current firmware version to confirm it is below 4.2.3
- Click 'Update' or 'Install Update' to upgrade to firmware version 4.2.3 or later
- Wait for the firmware update to complete and the device to reboot
- After reboot, verify the firmware version has been updated to 4.2.3 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24376 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-24376 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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