bajie vulnerabilities
Recent CVEs affecting bajie products. 6 tracked.
bajie has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2003-12-31. Highest priority: CVE-2001-0307 (score 55/100).
- CVE-2003-1543 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in Bajie Http Web Server 0.95zxe, 0.95zxc, and possibly others, allow
- CVE-2003-1511 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in Bajie Java HTTP Server 0.95 through 0.95zxv4 allows remote attacke
- CVE-2001-0308 HIGH 7.5 UPGRADE UploadServlet in Bajie HTTP JServer 0.78, and possibly other versions before 0.80, allows remote attackers to
- CVE-2001-0307 HIGH 7.5 UPGRADE Bajie HTTP JServer 0.78, and other versions before 0.80, allows remote attackers to execute arbitrary commands
- CVE-2000-0774 MEDIUM 5.0 DOWNGRADE The sample Java servlet "test" in Bajie HTTP web server 0.30a reveals the real pathname of the web document ro
- CVE-2000-0773 MEDIUM 5.0 DOWNGRADE Bajie HTTP web server 0.30a allows remote attackers to read arbitrary files via a URL that contains a "....",
FAQ
How do I fix bajie 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 bajie being exploited right now?
None of the tracked bajie CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which bajie CVE should I patch first?
CVE-2001-0307 currently ranks highest (55/100): Bajie HTTP JServer 0.78, and other versions before 0.80, allows remote attackers to execute arbitrary commands.