Mini Search Appliance vulnerabilitiesRanked by how likely they are to be used.

Product2 versions
The short answer

Mini Search Appliance is made by Google. We track 8 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Mini Search Appliance, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Mini Search Appliance vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Mini Search Appliance's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Mini Search Appliance 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.

50% or more10% to 49%Under 10%
  1. 41%

    The Saxon XSLT parser in Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to obtain sensitive information and execute arbitrary code via dangerous Java class methods in...

    CVSS7.5Published22 Nov 2005
  2. 19%

    Cross-site scripting (XSS) vulnerability in Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to inject arbitrary Javascript, and possibly other web script or HTML, via a...

    CVSS4.3Published22 Nov 2005
  3. 4.1%

    Google Mini 4.4.102.M.36 and earlier allows remote attackers to obtain sensitive information via a direct request for /search with an invalid client parameter, which reveals the path in an error message.

    CVSS5.0Published27 Sep 2006
  4. 3.6%

    Directory traversal vulnerability in Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to determine the existence of arbitrary files via a relative path from a style sheet...

    CVSS5.0Published22 Nov 2005
  5. 3.1%

    Cross-site scripting (XSS) vulnerability in Google Search Appliance and Google Mini allows remote attackers to inject arbitrary web script or HTML via a UTF-7 encoded q parameter.

    CVSS4.3Published2 Dec 2006
  6. 2.3%

    Cross-site scripting (XSS) vulnerability in Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to inject arbitrary Javascript, and possibly other web script or HTML, via the...

    CVSS4.3Published22 Nov 2005
  7. 2.0%

    Cross-site scripting (XSS) vulnerability in Google Mini Search Appliance 3.4.14 allows remote attackers to inject arbitrary web script or HTML via the ie parameter to the /search URI.

    CVSS4.3Published6 Oct 2007
  8. 1.8%

    Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to port scan arbitrary hosts via URLs with modified targets and ports, then comparing the resulting error messages to...

    CVSS5.0Published22 Nov 2005
EdgeProtect

Running Mini Search Appliance? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Mini Search Appliance, across 2 versions.

None of Mini Search Appliance's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Mini Search Appliance. 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.