Aura Messaging vulnerabilitiesRanked by how likely they are to be used.
Aura Messaging is made by Avaya. We track 2 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Aura Messaging, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Aura Messaging vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Aura Messaging's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Aura Messaging 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.
- 2.3%CVE-2016-5285High
A Null pointer dereference vulnerability exists in Mozilla Network Security Services due to a missing NULL check in PK11_SignWithSymKey / ssl3_ComputeRecordMACConstantTime, which could let a remote malicious user...
- 0.4%CVE-2020-7029High
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging.
Running Aura Messaging? 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
A Null pointer dereference vulnerability exists in Mozilla Network Security Services due to a missing NULL check in PK11_SignWithSymKey / ssl3_ComputeRecordMACConstantTime, which could let a remote malicious user cause a Denial of Service.
- Matched to
- Aura Messaging 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 Aura Messaging, across 3 versions.
None of Aura Messaging's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Aura Messaging. 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.