University of Minnesota vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

University of Minnesota has 10 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Gopherd, with 5. If you run University of Minnesota software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which University of Minnesota products have the most vulnerabilities?

Gopherd leads with 5 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Gopherd5
  2. Gopher3
  3. Mapserver2
Published vulnerabilities
Known exploited

Which University of Minnesota vulnerabilities are being exploited?

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

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

Exploit likelihood

Which University of Minnesota 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. 54%

    Buffer overflow in gopher client for Microsoft Internet Explorer 5.1 through 6.0, Proxy Server 2.0, or ISA Server 2000 allows remote attackers to execute arbitrary code via a gopher:// URL that redirects the user to...

    CVSS7.5Published3 Jul 2002
  2. 13%

    Buffer overflow in University of Minnesota (UMN) gopherd 2.x allows remote attackers to execute arbitrary commands via a DES key generation request (GDESkey) that contains a long ticket value.

    CVSS10.0Published20 Oct 2000
  3. 10%

    Multiple stack-based buffer overflows in University of Minnesota gopher client 3.0.9 allow remote malicious servers to execute arbitrary code via (1) a long "+VIEWS:" reply, which is not properly handled in the...

    CVSS7.5Published2 Sep 2005
  4. 5.0%

    Multiple buffer overflows in UMN gopher daemon (gopherd) 2.x and 3.x before 3.0.6 allows attackers to execute arbitrary code via (1) a long filename as a result of a LIST command, and (2) the GSisText function, which...

    CVSS7.5Published6 Oct 2003
  5. 3.5%

    Buffer overflow in the processLine function in maptemplate.c in MapServer before 4.10.3 allows attackers to cause a denial of service and possibly execute arbitrary code via a mapfile with a long layer name, group...

    CVSS7.5Published31 Aug 2007
  6. 3.0%

    Integer overflow in gopher daemon (gopherd) 3.0.3 allows remote attackers to cause a denial of service and possibly execute arbitrary code via crafted content of a certain size that triggers the overflow.

    CVSS7.5Published31 Dec 2004
  7. 2.3%

    Format string vulnerability in the log routine for gopher daemon (gopherd) 3.0.3 allows remote attackers to cause a denial of service and possibly execute arbitrary code.

    CVSS7.5Published31 Dec 2004
  8. 1.8%

    Vulnerabilities in UMN gopher and gopher+ versions 1.12 and 2.0x allow an intruder to read any files that can be accessed by the gopher daemon.

    CVSS10.0Published9 Aug 1993
  9. 1.6%

    Multiple cross-site scripting (XSS) vulnerabilities in MapServer before 4.10.3 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors involving the (1) processLine function in...

    CVSS4.3Published27 Aug 2007
  10. 0.5%

    gopher.c in the Gopher client 3.0.5 does not properly create temporary files, which allows local users to gain privileges.

    CVSS7.2Published3 Aug 2005
Every product

All University of Minnesota products we track.

2 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

This directory lists the 2 University of Minnesota products with at least one tracked version, of 3 in our catalogue.

Precursor Intelligence

Running University of Minnesota? 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 →

Our catalogue lists 10 published vulnerabilities across 3 products and 12 versions from University of Minnesota.

None of University of Minnesota's vulnerabilities is on the list of flaws known to be exploited today.

Gopherd, with 5 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the University of Minnesota products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.