Gzip vulnerabilitiesRanked by how likely they are to be used.

Product26 versions
The short answer

Gzip is made by Gnu. We track 11 published vulnerabilities in it, across 26 versions. None of them is on the list of flaws known to be exploited today. If you run Gzip, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Gzip vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Gzip 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. 5.2%

    An arbitrary file write vulnerability was found in GNU gzip's zgrep utility.

    CVSS8.8Published31 Aug 2022
  2. 4.8%

    Integer underflow in the unlzw function in unlzw.c in gzip before 1.4 on 64-bit platforms, as used in ncompress and probably others, allows remote attackers to cause a denial of service (application crash) or...

    CVSS6.8Published29 Jan 2010
  3. 4.2%

    The huft_build function in inflate.c in gzip before 1.3.13 creates a hufts (aka huffman) table that is too small, which allows remote attackers to cause a denial of service (application crash or infinite loop) or...

    CVSS6.8Published29 Jan 2010
  4. 3.6%

    Directory traversal vulnerability in gunzip -N in gzip 1.2.4 through 1.3.5 allows remote attackers to write to arbitrary directories via a ..

    CVSS5.0Published2 May 2005
  5. 3.1%

    gzexe in gzip 1.3.3 and earlier will execute an argument when the creation of a temp file fails instead of exiting the program, which could allow remote attackers or local users to execute arbitrary commands, a...

    CVSS10.0Published6 Dec 2004
  6. 3.1%

    Buffer overflows in gzip 1.3x, 1.2.4, and other versions might allow attackers to execute code via a long file name, possibly remotely if gzip is run on an FTP server.

    CVSS7.5Published18 Nov 2001
  7. 0.7%

    Race condition in gzip 1.2.4, 1.3.3, and earlier, when decompressing a gzipped file, allows local users to modify permissions of arbitrary files via a hard link attack on a file while it is being decompressed, whose...

    CVSS3.7Published2 May 2005
  8. 0.6%

    gzip before 1.3 in Solaris 8, when called with the -f or -force flags, will change the permissions of files that are hard linked to the target files, which allows local users to view or modify these files.

    CVSS2.1Published4 Oct 2004
  9. 0.5%

    zgrep in gzip before 1.3.5 does not properly sanitize arguments, which allows local users to execute arbitrary commands via filenames that are injected into a sed script.

    CVSS4.6Published13 May 2005
  10. 0.4%

    znew in the gzip package allows local users to overwrite arbitrary files via a symlink attack on temporary files.

    CVSS2.1Published2 Jul 2003
Precursor Intelligence

Running Gzip? 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 11 published vulnerabilities listed under the name Gzip, across 26 versions.

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

Create a Precursor Intelligence account and track Gzip. 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.