Traffix Signaling Delivery Controller vulnerabilitiesAnd the versions its exploited flaws hit.
Traffix Signaling Delivery Controller is made by F5. We track 30 published vulnerabilities in it, across 11 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 28 January 2022. If you run Traffix Signaling Delivery Controller, check your version against the exploited flaws below and patch those first.
The most recent Traffix Signaling Delivery Controller flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022. We keep watching the known-exploited list.
Which versions of Traffix Signaling Delivery Controller do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2014-6271Exploited list, 28 Jan 2022
GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
3.3.23.4.13.5.14.0.0 to 4.0.54.1.0 - CVE-2014-7169Exploited list, 28 Jan 2022
GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
3.3.23.4.13.5.14.0.0 to 4.0.54.1.0
Which Traffix Signaling Delivery Controller vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
- 9.8GNU Bourne-Again Shell (Bash) Arbitrary Code Execution Vulnerability
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
Which Traffix Signaling Delivery Controller 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.
- >99%
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute arbitrary code via a crafted environment, as demonstrated by...
- >99%
GNU Bash through 4.3 bash43-025 processes trailing strings after certain malformed function definitions in the values of environment variables, which allows remote attackers to write to files or possibly have unknown...
- 99%CVE-2019-11477High
Jonathan Looney discovered that the TCP_SKB_CB(skb)->tcp_gso_segs value was subject to an integer overflow in the Linux kernel when handling TCP Selective Acknowledgments (SACKs).
- 95%CVE-2019-11478High
Jonathan Looney discovered that the TCP retransmission queue implementation in tcp_fragment in the Linux kernel could be fragmented when handling certain TCP Selective Acknowledgment (SACK) sequences.
- 92%CVE-2019-11479High
Jonathan Looney discovered that the Linux kernel default MSS is hard-coded to 48 bytes.
- 50%CVE-2019-5436High
A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.
- 25%CVE-2002-20001High
The Diffie-Hellman Key Agreement Protocol allows remote attackers (from the client side) to send arbitrary numbers that are actually not public keys, and trigger expensive server-side DHE modular-exponentiation...
- 17%CVE-2019-1559Medium
If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0...
- 8.2%CVE-2018-1320High
Apache Thrift Java client library versions 0.5.0 through 0.11.0 can bypass SASL negotiation isComplete validation in the org.apache.thrift.transport.TSaslTransport class.
- 6.8%CVE-2018-16229High
The DCCP parser in tcpdump before 4.9.3 has a buffer over-read in print-dccp.c:dccp_print_option().
Running Traffix Signaling Delivery Controller? 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 flaw being exploited affects software Acme tracks
GNU Bash through 4.3 processes trailing strings after function definitions in the values of environment variables, which allows remote attackers to execute code.
- Matched to
- Traffix Signaling Delivery Controller on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 30 published vulnerabilities listed under the name Traffix Signaling Delivery Controller, across 11 versions. The most recent Traffix Signaling Delivery Controller flaw added to the known-exploited list is CVE-2014-6271, on 28 January 2022.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2014-6271 and CVE-2014-7169.
Each flaw names its own versions, usually as ranges. The newest, CVE-2014-6271, affects 3.3.2, 3.4.1, 3.5.1, 4.0.0 to 4.0.5 and more. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Traffix Signaling Delivery Controller. 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.