Tim 4r-Ie Firmware vulnerabilitiesRanked by how likely they are to be used.
Tim 4r-Ie Firmware is made by Siemens. We track 9 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Tim 4r-Ie Firmware, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Tim 4r-Ie Firmware vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Tim 4r-Ie Firmware's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Tim 4r-Ie Firmware 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.
- 31%CVE-2015-7855Medium
The decodenetnum function in ntpd in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service (assertion failure) via a 6 or mode 7 packet containing a long data value.
- 17%CVE-2016-4953High
ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (ephemeral-association demobilization) by sending a spoofed crypto-NAK packet with incorrect authentication data at a certain time.
- 13%CVE-2016-4954High
The process_packet function in ntp_proto.c in ntpd in NTP 4.x before 4.2.8p8 allows remote attackers to cause a denial of service (peer-variable modification) by sending spoofed packets from many source IP addresses...
- 12%CVE-2015-7705Critical
The rate limiting feature in NTP 4.x before 4.2.8p4 and 4.3.x before 4.3.77 allows remote attackers to have unspecified impact via a large number of crafted requests.
- 6.3%CVE-2015-7977Medium
ntpd in NTP before 4.2.8p6 and 4.3.x before 4.3.90 allows remote attackers to cause a denial of service (NULL pointer dereference) via a ntpdc reslist command.
- 6.1%CVE-2015-5219High
The ULOGTOD function in ntp.d in SNTP before 4.2.7p366 does not properly perform type conversions from a precision value to a double, which allows remote attackers to cause a denial of service (infinite loop) via a...
- 5.7%CVE-2015-7974High
NTP 4.x before 4.2.8p6 and 4.3.x before 4.3.90 do not verify peer associations of symmetric keys when authenticating packets, which might allow remote attackers to conduct impersonation attacks via an arbitrary...
- 3.4%CVE-2015-7973Medium
NTP before 4.2.8p6 and 4.3.x before 4.3.90, when configured in broadcast mode, allows man-in-the-middle attackers to conduct replay attacks by sniffing the network.
- 1.1%CVE-2019-10939Critical
A vulnerability has been identified in TIM 3V-IE (incl.
Running Tim 4r-Ie Firmware? 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
The decodenetnum function in ntpd in NTP 4.2.x before 4.2.8p4, and 4.3.x before 4.3.77 allows remote attackers to cause a denial of service (assertion failure) via a 6 or mode 7 packet containing a long data value.
- Matched to
- Tim 4r-Ie Firmware 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 9 published vulnerabilities listed under the name Tim 4r-Ie Firmware, across 1 version.
None of Tim 4r-Ie Firmware's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Tim 4r-Ie Firmware. 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.