Er-4 vulnerabilitiesRanked by how likely they are to be used.
Er-4 is made by UI. We track 2 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. UI lists newer releases under their own names, such as Er-4 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is Er-4 listed under other names? Yes.
UI also lists Er-4 under more specific names, such as Er-4 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 Er-4 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Er-4's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Er-4 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.
- 5.1%CVE-2019-16889High
Ubiquiti EdgeMAX devices before 2.0.3 allow remote attackers to cause a denial of service (disk consumption) because *.cache files in /var/run/beaker/container_file/ are created when providing a valid length payload...
Running Er-4? 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
Ubiquiti EdgeMAX devices before 2.0.3 allow remote attackers to cause a denial of service (disk consumption) because *.cache files in /var/run/beaker/container_file/ are created when providing a valid length payload of 249 characters or fewer to the beaker.session.id cookie in a GET header. The attacker can use a long series of unique session IDs.
- Matched to
- Er-4 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 2 published vulnerabilities listed under the name Er-4, across 0 versions.
None of Er-4's vulnerabilities is on the list of flaws known to be exploited today.
UI also lists Er-4 under more specific names, such as Er-4 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 Er-4. 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.