Communications Session Router vulnerabilitiesRanked by how likely they are to be used.
Communications Session Router is made by Oracle. We track 3 published vulnerabilities in it, across 8 versions. None of them is on the list of flaws known to be exploited today. If you run Communications Session Router, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Communications Session Router vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Communications Session Router's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Communications Session Router 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...
- 7.1%CVE-2020-1971Medium
The X.509 GeneralName type is a generic type for representing different types of names.
- 5.2%CVE-2020-8203High
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
Running Communications Session Router? 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
- Communications Session Router 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 3 published vulnerabilities listed under the name Communications Session Router, across 8 versions.
None of Communications Session Router's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Communications Session Router. 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.