GNU Libidn
By the Year
In 2024 there have been 0 vulnerabilities in GNU Libidn . Libidn did not have any published security vulnerabilities last year.
Year | Vulnerabilities | Average Score |
---|---|---|
2024 | 0 | 0.00 |
2023 | 0 | 0.00 |
2022 | 0 | 0.00 |
2021 | 0 | 0.00 |
2020 | 0 | 0.00 |
2019 | 0 | 0.00 |
2018 | 0 | 0.00 |
It may take a day or so for new Libidn vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent GNU Libidn Security Vulnerabilities
The stringprep_utf8_nfkc_normalize function in lib/nfkc.c in libidn before 1.33
CVE-2016-6263
7.5 - High
- September 07, 2016
The stringprep_utf8_nfkc_normalize function in lib/nfkc.c in libidn before 1.33 allows context-dependent attackers to cause a denial of service (out-of-bounds read and crash) via crafted UTF-8 data.
Out-of-bounds Read
idn in libidn before 1.33 might
CVE-2016-6262
7.5 - High
- September 07, 2016
idn in libidn before 1.33 might allow remote attackers to obtain sensitive memory information by reading a zero byte as input, which triggers an out-of-bounds read, a different vulnerability than CVE-2015-8948.
Out-of-bounds Read
The idna_to_ascii_4i function in lib/idna.c in libidn before 1.33
CVE-2016-6261
7.5 - High
- September 07, 2016
The idna_to_ascii_4i function in lib/idna.c in libidn before 1.33 allows context-dependent attackers to cause a denial of service (out-of-bounds read and crash) via 64 bytes of input.
Out-of-bounds Read
idn in GNU libidn before 1.33 might
CVE-2015-8948
7.5 - High
- September 07, 2016
idn in GNU libidn before 1.33 might allow remote attackers to obtain sensitive memory information by reading a zero byte as input, which triggers an out-of-bounds read.
Out-of-bounds Read
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for GNU Libidn or by GNU? Click the Watch button to subscribe.