International Components for Unicode vulnerabilitiesRanked by how likely they are to be used.

Product112 versions
The short answer

International Components for Unicode is made by Icu-Project. We track 21 published vulnerabilities in it, across 112 versions. None of them is on the list of flaws known to be exploited today. If you run International Components for Unicode, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which International Components for Unicode vulnerabilities are being exploited?

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

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

Exploit likelihood

Which International Components for Unicode 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. 25%

    The resolveImplicitLevels function in common/ubidi.c in the Unicode Bidirectional Algorithm implementation in ICU4C in International Components for Unicode (ICU) before 55.1 does not properly track directionally...

    CVSS7.5Published25 May 2015
  2. 24%

    The resolveImplicitLevels function in common/ubidi.c in the Unicode Bidirectional Algorithm implementation in ICU4C in International Components for Unicode (ICU) before 55.1 uses an integer data type that is...

    CVSS7.5Published25 May 2015
  3. 8.0%

    Stack-based buffer overflow in the _canonicalize function in common/uloc.c in International Components for Unicode (ICU) before 49.1 allows remote attackers to execute arbitrary code via a crafted locale ID that is...

    CVSS7.5Published21 Jun 2012
  4. 5.8%

    Stack-based buffer overflow in the Locale class in common/locid.cpp in International Components for Unicode (ICU) through 57.1 for C/C++ allows remote attackers to cause a denial of service (application crash) or...

    CVSS9.8Published17 Sep 2016
  5. 5.6%

    Stack-based buffer overflow in the ures_getByKeyWithFallback function in common/uresbund.cpp in International Components for Unicode (ICU) before 54.1 for C/C++ allows remote attackers to cause a denial of service or...

    CVSS9.8Published4 Jan 2017
  6. 5.1%

    Double free in i18n/zonemeta.cpp in International Components for Unicode (ICU) for C/C++ through 59.1 allows remote attackers to execute arbitrary code via a crafted string, aka a "redundant UVector entry clean up...

    CVSS9.8Published16 Oct 2017
  7. 5.0%

    The uloc_acceptLanguageFromHTTP function in common/uloc.cpp in International Components for Unicode (ICU) through 57.1 for C/C++ does not ensure that there is a '\0' character at the end of a certain temporary array,...

    CVSS9.8Published25 Jul 2016
  8. 4.6%

    International Components for Unicode (ICU) for C/C++ before 2017-02-13 has an out-of-bounds write caused by a heap-based buffer overflow related to the utf8TextAccess function in common/utext.cpp and the...

    CVSS7.5Published14 Apr 2017
  9. 4.5%

    The ucnv_UTF8FromUTF8 function in ucnv_u8.cpp in International Components for Unicode (ICU) for C/C++ through 60.1 mishandles ucnv_convertEx calls for UTF-8 to UTF-8 conversion, which allows remote attackers to cause...

    CVSS9.8Published10 Dec 2017
  10. 4.4%

    International Components for Unicode (ICU) for C/C++ before 2017-02-13 has an out-of-bounds write caused by a heap-based buffer overflow related to the utf8TextAccess function in common/utext.cpp and the...

    CVSS7.5Published14 Apr 2017
Precursor Intelligence

Running International Components for Unicode? 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 21 published vulnerabilities listed under the name International Components for Unicode, across 112 versions.

None of International Components for Unicode's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track International Components for Unicode. 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.