P B X vulnerabilitiesRanked by how likely they are to be used.
P B X is made by Asterisk. We track 1 published vulnerability in it, across 4 versions. None of them is on the list of flaws known to be exploited today. If you run P B X, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which P B X vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of P B X's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Running P B X? 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
Asterisk Open Source 1.2.x before 1.2.32, 1.4.x before 1.4.24.1, and 1.6.0.x before 1.6.0.8; Asterisk Business Edition A.x.x, B.x.x before B.2.5.8, C.1.x.x before C.1.10.5, and C.2.x.x before C.2.3.3; s800i 1.3.x before 1.3.0.2; and Trixbox PBX 2.6.1, when Digest authentication and authalwaysreject are enabled, generates different responses depending on whether a SIP username is valid, which allows remote attackers to enumerate valid usernames.
- Matched to
- P B X 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 1 published vulnerability listed under the name P B X, across 4 versions.
None of P B X's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track P B X. 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.