jabberstudio vulnerabilities
Recent CVEs affecting jabberstudio products. 5 tracked.
jabberstudio has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2006-03-21. Highest priority: CVE-2006-1329 (score 39/100).
- CVE-2006-1329 MEDIUM 5.0 UPGRADE The SASL negotiation in Jabber Studio jabberd before 2.0s11 allows remote attackers to cause a denial of servi
- CVE-2004-2391 MEDIUM 5.0 DOWNGRADE Jabber Gadu-Gadu Transport (a.k.a
- CVE-2004-2390 MEDIUM 5.0 DOWNGRADE The roster import functionality in Jabber Gadu-Gadu Transport (a.k.a
- CVE-2004-2389 MEDIUM 5.0 DOWNGRADE Unknown vulnerability in Jabber Gadu-Gadu Transport (a.k.a
- CVE-2004-1378 MEDIUM 5.0 DOWNGRADE DOWNGRADE The expat XML parser code, as used in the open source Jabber (jabberd) 1.4.3 and earlier, jadc2s 0.9.0 and ear
FAQ
How do I fix jabberstudio vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is jabberstudio being exploited right now?
None of the tracked jabberstudio CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jabberstudio CVE should I patch first?
CVE-2006-1329 currently ranks highest (39/100): The SASL negotiation in Jabber Studio jabberd before 2.0s11 allows remote attackers to cause a denial of servi.