Virtualized Voice Browser vulnerabilitiesAnd the versions its exploited flaws hit.
Virtualized Voice Browser is made by Cisco. We track 4 published vulnerabilities in it, across 5 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 10 December 2021. If you run Virtualized Voice Browser, check your version against the exploited flaws below and patch those first.
The most recent Virtualized Voice Browser flaw added to the known-exploited list is CVE-2021-44228, on 10 December 2021. We keep watching the known-exploited list.
Which versions of Virtualized Voice Browser do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "before 12.5(1)" means every version up to, but not including, 12.5(1). Find your version, then patch.
- CVE-2021-44228Exploited list, 10 Dec 2021
Apache Log4j2 Remote Code Execution Vulnerability
before 12.5(1)
Which Virtualized Voice Browser vulnerabilities are being exploited?
1 flaw is 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.
- 10.0Apache Log4j2 Remote Code Execution Vulnerability
Apache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.
Which Virtualized Voice Browser 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.4%CVE-2024-20253Critical
A vulnerability in multiple Cisco Unified Communications and Contact Center Solutions products could allow an unauthenticated, remote attacker to execute arbitrary code on an affected device.
- 2.0%CVE-2017-6779High
Multiple Cisco products are affected by a vulnerability in local file management for certain system log files of Cisco collaboration products that could allow an unauthenticated, remote attacker to cause high disk...
- 0.8%CVE-2021-1575Medium
A vulnerability in the web-based management interface of Cisco Virtualized Voice Browser could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface.
Running Virtualized Voice Browser? 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
Apache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution.
- Matched to
- Virtualized Voice Browser 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 4 published vulnerabilities listed under the name Virtualized Voice Browser, across 5 versions. The most recent Virtualized Voice Browser flaw added to the known-exploited list is CVE-2021-44228, on 10 December 2021.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2021-44228.
Each flaw names its own versions, usually as ranges. The newest, CVE-2021-44228, affects before 12.5(1). The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Virtualized Voice Browser. 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.