Icewall File Manager vulnerabilitiesRanked by how likely they are to be used.

Product1 versions
The short answer

Icewall File Manager is made by HP. We track 14 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Icewall File Manager, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Icewall File Manager vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Icewall File Manager 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. 7.2%

    Heap-based buffer overflow in the xmlDictComputeFastQKey function in dict.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service via unspecified vectors.

    CVSS5.0Published15 Dec 2015
  2. 7.2%

    Heap-based buffer overflow in the xmlParseXmlDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service via unspecified vectors related to extracting errors...

    CVSS5.0Published15 Dec 2015
  3. 7.0%

    The xmlStringGetNodeList function in tree.c in libxml2 2.9.3 and earlier, when used in recovery mode, allows context-dependent attackers to cause a denial of service (infinite recursion, stack consumption, and...

    CVSS7.5Published17 May 2016
  4. 6.4%

    Heap-based buffer overflow in the xmlGROW function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive process memory information via unspecified vectors.

    CVSS5.0Published15 Dec 2015
  5. 5.9%

    The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service (out-of-bounds heap read) via unspecified vectors related to incorrect entities boundaries...

    CVSS5.0Published15 Dec 2015
  6. 5.9%

    The xmlParseXMLDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive information via an (1) unterminated encoding value or (2) incomplete XML declaration in XML...

    CVSS5.0Published15 Dec 2015
  7. 5.4%

    The xmlNextChar function in libxml2 2.9.2 does not properly check the state, which allows context-dependent attackers to cause a denial of service (heap-based buffer over-read and application crash) or obtain...

    CVSS6.4Published15 Dec 2015
  8. 5.1%

    The (1) xmlParserEntityCheck and (2) xmlParseAttValueComplex functions in parser.c in libxml2 2.9.3 do not properly keep track of the recursion depth, which allows context-dependent attackers to cause a denial of...

    CVSS7.5Published17 May 2016
  9. 4.7%

    The xmlParseConditionalSections function in parser.c in libxml2 does not properly skip intermediary entities when it stops parsing invalid input, which allows context-dependent attackers to cause a denial of service...

    CVSS6.8Published18 Nov 2015
  10. 4.5%

    The xmlStringLenDecodeEntities function in parser.c in libxml2 before 2.9.3 does not properly prevent entity expansion, which allows context-dependent attackers to cause a denial of service (CPU consumption) via...

    CVSS7.1Published15 Dec 2015
Precursor Intelligence

Running Icewall File Manager? 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 14 published vulnerabilities listed under the name Icewall File Manager, across 1 version.

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

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