File Project vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

File Project has 18 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is File, with 18. If you run File Project software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which File Project products have the most vulnerabilities?

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

  1. File18
Published vulnerabilities
Known exploited

Which File Project vulnerabilities are being exploited?

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

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

Exploit likelihood

Which File Project 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. 15%

    The cdf_check_stream_offset function in cdf.c in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, relies on incorrect sector-size data, which allows remote attackers...

    CVSS4.3Published9 Jul 2014
  2. 15%

    The cdf_read_property_info function in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, does not properly validate a stream offset, which allows remote attackers to...

    CVSS4.3Published9 Jul 2014
  3. 11%

    The cdf_count_chain function in cdf.c in file before 5.19, as used in the Fileinfo component in PHP before 5.4.30 and 5.5.x before 5.5.14, does not properly validate sector-count data, which allows remote attackers...

    CVSS4.3Published9 Jul 2014
  4. 5.9%

    softmagic.c in file before 5.21 does not properly limit recursion, which allows remote attackers to cause a denial of service (CPU consumption or crash) via unspecified vectors.

    CVSS5.0Published17 Dec 2014
  5. 5.5%

    The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field...

    CVSS5.0Published30 Mar 2015
  6. 4.7%

    The ELF parser in file 5.08 through 5.21 allows remote attackers to cause a denial of service via a large number of notes.

    CVSS5.0Published21 Jan 2015
  7. 4.6%

    readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available...

    CVSS7.5Published30 Mar 2015
  8. 4.4%

    The ELF parser (readelf.c) in file before 5.21 allows remote attackers to cause a denial of service (CPU consumption or crash) via a large number of (1) program or (2) section headers or (3) invalid capabilities.

    CVSS5.0Published17 Dec 2014
  9. 4.3%

    softmagic.c in file before 5.17 and libmagic allows context-dependent attackers to cause a denial of service (out-of-bounds memory access and crash) via crafted offsets in the softmagic of a PE executable.

    CVSS4.3Published14 Mar 2014
  10. 3.5%

    do_core_note in readelf.c in libmagic.a in file 5.35 allows remote attackers to cause a denial of service (stack corruption and application crash) or possibly have unspecified other impact.

    CVSS8.8Published18 Feb 2019
Every product

All File Project products we track.

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

Precursor Intelligence

Running File Project? 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 18 published vulnerabilities across 1 product and 85 versions from File Project.

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

File, with 18 published vulnerabilities. Its own page lists the ones known to be exploited.

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