dbcve.org
Dir 816 FirmwareOperating system · Dlink

CVE-2024-13106

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was found in D-Link DIR-816 A2 1.10CNB05_R1B011D88210 and classified as critical. Affected by this issue is some unknown functionality of the file /goform/form2IPQoSTcAdd of the component IP QoS Handler. The manipulation leads to improper access controls. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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 · moderate confidence

The D-Link DIR-816 A2 router firmware 1.10CNB05_R1B011D88210 contains an improper access control vulnerability in the IP QoS Handler component (/goform/form2IPQoSTcAdd). This allows remote attackers to manipulate QoS settings without authentication due to missing or inadequate access controls on the web interface form handler.

MitigationApply vendor firmware updates when available; until then, restrict router web management interface access to trusted networks only or disable remote management.

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
Dir 816 FirmwareOperating system
Affected:= 1.10cnb05_r1b011d88210

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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. Verify firmware version
    Log into the router web interface and navigate to the Status or System Info page to view the firmware version. Alternatively, check via telnet/SSH if enabled by running 'cat /proc/version' or checking /etc/version file.
    Affected if firmware version displayed is exactly 1.10cnb05_r1b011d88210
  2. Confirm IP QoS feature exists
    Access the router web interface and look for IP QoS or QoS settings in the Advanced or Bandwidth Management sections. The vulnerable endpoint /goform/form2IPQoSTcAdd handles these requests.
    Affected if IP QoS or Traffic Control settings page is present and accessible in the web interface
  3. Check web interface accessibility
    Determine if the router web management interface is accessible from untrusted networks. Attempt to access the router IP from an external network or verify remote management settings in the Administration or Management section.
    Affected if web interface is accessible from outside the trusted local network or remote management is enabled

You are affected if your D-Link DIR-816 firmware is version 1.10cnb05_r1b011d88210 and the router web interface is accessible (especially remotely), allowing unauthenticated manipulation of QoS settings through the /goform/form2IPQoSTcAdd endpoint.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available; until then, restrict router web management interface access to trusted networks only or disable remote management.

Recommended fix Moderate confidence

DIR-816 A2 latest available firmware (check www.dlink.com for current version)

  1. 1. Visit the official D-Link support page at www.dlink.com and navigate to the DIR-816 A2 product support section.
  2. 2. Locate and download the latest firmware version available for the DIR-816 A2 router.
  3. 3. Access the router's web administration interface by entering the router's IP address (typically 192.168.0.1) in a web browser.
  4. 4. Log in with administrative credentials (default credentials are often admin/admin or admin/password - check router label or documentation).
  5. 5. Navigate to the System or Administration settings section, then locate the Firmware Upgrade or Update option.
  6. 6. Click Browse/Choose File and select the downloaded firmware file, then initiate the upgrade process.
  7. 7. Wait for the firmware upload to complete and the router to reboot - do not power off the router during this process.
  8. 8. After reboot, verify the new firmware version in the router's admin interface to confirm successful upgrade.
Caveat Firmware upgrades on older routers may reset configuration to defaults; back up current settings before upgrading and re-apply after upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 816 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-13106 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