Threat Intelligence Exchange Server vulnerabilitiesRanked by how likely they are to be used.
Threat Intelligence Exchange Server is made by Mcafee. We track 7 published vulnerabilities in it, across 9 versions. None of them is on the list of flaws known to be exploited today. If you run Threat Intelligence Exchange Server, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Threat Intelligence Exchange Server vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Threat Intelligence Exchange Server's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Threat Intelligence Exchange Server 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.
- 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...
- 4.9%CVE-2020-2781Medium
Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: JSSE).
- 4.9%CVE-2020-2830Medium
Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Concurrency).
- 1.7%CVE-2019-3738Medium
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to a Missing Required Cryptographic Step vulnerability.
- 0.7%CVE-2019-3641Medium
Abuse of Authorization vulnerability in APIs exposed by TIE server in McAfee Threat Intelligence Exchange Server (TIE Server) 3.0.0 allows remote authenticated users to modify stored reputation data via specially...
- 0.7%CVE-2018-6695Medium
SSH host keys generation vulnerability in the server in McAfee Threat Intelligence Exchange Server (TIE Server) 1.3.0, 2.0.x, 2.1.x, 2.2.0 allows man-in-the-middle attackers to spoof servers via acquiring keys from...
- 0.5%CVE-2020-0543Medium
Incomplete cleanup from specific special register read operations in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.
Running Threat Intelligence Exchange Server? 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
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 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).
- Matched to
- Threat Intelligence Exchange Server 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 7 published vulnerabilities listed under the name Threat Intelligence Exchange Server, across 9 versions.
None of Threat Intelligence Exchange Server's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Threat Intelligence Exchange Server. 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.