Lr350 vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Lr350 is made by Totolink. We track 29 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Totolink lists newer releases under their own names, such as Lr350 Firmware, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Lr350 listed under other names? Yes.

Totolink also lists Lr350 under more specific names, such as Lr350 Firmware. 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 Lr350 vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Lr350 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. 6.1%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 was discovered to contain a stack overflow via the http_host parameter in the function loginAuth.

    CVSS9.8Published24 May 2024
  2. 3.2%

    A vulnerability has been found in TOTOLINK LR350 9.3.5u.6369_B20220309 and classified as critical.

    CVSS5.3Published30 Jul 2024
  3. 2.4%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter command in the setTracerouteCfg function.

    CVSS8.8Published23 Nov 2022
  4. 2.3%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a pre-authentication buffer overflow in the main function via long post data.

    CVSS9.8Published23 Nov 2022
  5. 2.2%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter text in the setSmsCfg function.

    CVSS8.8Published23 Nov 2022
  6. 2.2%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter ip in the setDiagnosisCfg function.

    CVSS8.8Published23 Nov 2022
  7. 2.2%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter pppoeUser in the setOpModeCfg function.

    CVSS8.8Published23 Nov 2022
  8. 2.2%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter sPort/ePort in the setIpPortFilterRules function.

    CVSS8.8Published23 Nov 2022
  9. 2.2%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 contains a post-authentication buffer overflow via parameter week, sTime, and eTime in the setParentalRules function.

    CVSS8.8Published23 Nov 2022
  10. 2.0%

    TOTOLINK LR350 V9.3.5u.6369_B20220309 was discovered to contain a command injection vulnerability via the FileName parameter in the UploadFirmwareFile function.

    CVSS9.8Published7 Jul 2023
Precursor Intelligence

Running Lr350? 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 29 published vulnerabilities listed under the name Lr350, across 0 versions.

None of Lr350's vulnerabilities is on the list of flaws known to be exploited today.

Totolink also lists Lr350 under more specific names, such as Lr350 Firmware. 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 Lr350. 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.