omnihttpd vulnerabilities and fixes
Recent CVEs affecting omnihttpd, with upgrade or downgrade steps. 7 tracked.
omnihttpd has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2003-06-09. Highest priority: CVE-2001-0113 (score 64/100).
- CVE-2002-1455 MEDIUM 4.3 MITIGATE Multiple cross-site scripting (XSS) vulnerabilities in OmniHTTPd allow remote attackers to insert script or HT
- CVE-2002-1035 MEDIUM 5.0 DOWNGRADE Omnicron OmniHTTPd 2.09 allows remote attackers to cause a denial of service (crash) via an HTTP request with
- CVE-2001-0778 MEDIUM 5.0 UPGRADE OmniHTTPd 2.0.8 and earlier allow remote attackers to obtain source code via a GET request with the URL-encode
- CVE-2001-0777 MEDIUM 5.0 DOWNGRADE Omnicron OmniHTTPd 2.0.8 allows remote attackers to cause a denial of service (memory exhaustion) via a series
- CVE-2001-0613 MEDIUM 5.0 UPGRADE Omnicron Technologies OmniHTTPD Professional 2.08 and earlier allows a remote attacker to create a denial of s
- CVE-2001-0114 MEDIUM 5.0 DOWNGRADE statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to overwrite arbitrary files via the cgidir parameter
- CVE-2001-0113 HIGH 10.0 DOWNGRADE statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to execute arbitrary commands via the mostbrowsers pa
FAQ
How do I fix omnihttpd 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 omnihttpd being exploited right now?
None of the tracked omnihttpd CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which omnihttpd CVE should I patch first?
CVE-2001-0113 currently ranks highest (64/100): statsconfig.pl in OmniHTTPd 2.07 allows remote attackers to execute arbitrary commands via the mostbrowsers pa.