Gt-Ac5300 vulnerabilitiesRanked by how likely they are to be used.
Gt-Ac5300 is made by Asus. We track 8 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Asus lists newer releases under their own names, such as Gt-Ac5300 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is Gt-Ac5300 listed under other names? Yes.
Asus also lists Gt-Ac5300 under more specific names, such as Gt-Ac5300 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.
Which Gt-Ac5300 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Gt-Ac5300's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Gt-Ac5300 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.
- 3.8%CVE-2018-20334Critical
An issue was discovered in ASUSWRT 3.0.0.4.384.20308.
- 2.2%CVE-2018-17022High
Stack-based buffer overflow on the ASUS GT-AC5300 router through 3.0.0.4.384_32738 allows remote attackers to cause a denial of service (device crash) or possibly have unspecified other impact by setting a long...
- 2.1%CVE-2018-17020High
ASUS GT-AC5300 devices with firmware through 3.0.0.4.384_32738 allow remote attackers to cause a denial of service via a single "GET / HTTP/1.1\r\n" line.
- 1.5%CVE-2018-17127High
blocking_request.cgi on ASUS GT-AC5300 devices through 3.0.0.4.384_32738 allows remote attackers to cause a denial of service (NULL pointer dereference and device crash) via a request that lacks a timestap parameter.
- 1.4%CVE-2018-20335High
An issue was discovered in ASUSWRT 3.0.0.4.384.20308.
- 1.2%CVE-2018-20333High
An issue was discovered in ASUSWRT 3.0.0.4.384.20308.
- 1.1%CVE-2018-17021Medium
Cross-site scripting (XSS) vulnerability on ASUS GT-AC5300 devices with firmware through 3.0.0.4.384_32738 allows remote attackers to inject arbitrary web script or HTML via the appGet.cgi hook parameter.
- 0.6%CVE-2018-17023High
Cross-site request forgery (CSRF) vulnerability on ASUS GT-AC5300 routers with firmware through 3.0.0.4.384_32738 allows remote attackers to hijack the authentication of administrators for requests that change the...
Running Gt-Ac5300? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 new flaw affects software Acme tracks
An issue was discovered in ASUSWRT 3.0.0.4.384.20308. When processing the /start_apply.htm POST data, there is a command injection issue via shell metacharacters in the fb_email parameter. By using this issue, an attacker can control the router and get shell.
- Matched to
- Gt-Ac5300 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Gt-Ac5300, across 0 versions.
None of Gt-Ac5300's vulnerabilities is on the list of flaws known to be exploited today.
Asus also lists Gt-Ac5300 under more specific names, such as Gt-Ac5300 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 Gt-Ac5300. 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.