Dir-600m vulnerabilitiesRanked by how likely they are to be used.

Product1 versions
The short answer

Dir-600m is made by Dlink. We track 8 published vulnerabilities listed under that exact name, across 1 version. None of them is on the list of flaws known to be exploited today. Dlink lists newer releases under their own names, such as Dir-600m Firmware, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Dir-600m listed under other names? Yes.

Dlink also lists Dir-600m under more specific names, such as Dir-600m Firmware and Dir-600m C1. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Dir-600m vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Dir-600m's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Dir-600m flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 85%

    login.cgi on D-Link DIR-600M devices with firmware 3.04 allows remote attackers to bypass authentication by entering more than 20 blank spaces in the password field during an admin login attempt.

    CVSS8.8Published21 May 2017
  2. 67%

    An issue was discovered on D-Link DIR-600M 3.02, 3.03, 3.04, and 3.06 devices.

    CVSS9.8Published8 Aug 2019
  3. 2.7%

    ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, has been found in D-Link DIR-600M C1 3.08.

    CVSS7.5Published23 Feb 2024
  4. 2.7%

    D-Link DIR-600M C1 3.04 devices allow authentication bypass via a direct request to the wan.htm page.

    CVSS9.8Published11 Feb 2019
  5. 1.2%

    D-Link DSL 2730-U IN_1.10 and IN_1.11 and DIR-600M 3.04 devices have the domain.name string in the DNS resolver search path by default, which allows remote attackers to provide valid DNS responses (and also offer...

    CVSS7.5Published8 Jun 2020
  6. 1.1%

    On D-Link DIR-600M devices before C1_v3.05ENB01_beta_20170306, XSS was found in the form2userconfig.cgi username parameter.

    CVSS6.1Published20 Jul 2017
  7. 0.9%

    D-Link DIR-600M devices allow XSS via the Hostname and Username fields in the Dynamic DNS Configuration page.

    CVSS5.4Published12 Sep 2018
  8. 0.7%

    CSRF exists on D-Link DIR-600M Rev. Cx devices before v3.05ENB01_beta_20170306.

    CVSS8.8Published22 Mar 2017
Precursor Intelligence

Running Dir-600m? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Dir-600m, across 1 version.

None of Dir-600m's vulnerabilities is on the list of flaws known to be exploited today.

Dlink also lists Dir-600m under more specific names, such as Dir-600m Firmware and Dir-600m C1. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Dir-600m. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.