CVE-2017-14061 json
Integer overflow in the _isBidi function in bidi.c in Libidn2 before 2.0.4 allows remote attackers to cause a denial of service or possibly…
published 9y ago modified 4mo ago also EUVD-2017-5575
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Integer overflow in the _isBidi function in bidi.c in Libidn2 before 2.0.4 allows remote attackers to cause a denial of service or possibly have unspecified other impact.
Patch / fix
Is CVE-2017-14061 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-14061 updated cvss 3.3
libidn2: integer overflow in bidi.c/_isBidi()
-
Red Hat Enterprise Linux 5 libidn Red Hat Enterprise Linux 6 libidn Red Hat Enterprise Linux 7 libidn, emacs-libidnnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.40% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
-
gitlab.com
/libidn/libidn2/commit/16853b6973a1e72fee2b7cccda85472cb9951305
patch, third-party-advisory
-
gitlab.com
/libidn/libidn2/blob/master/NEWS
release-notes, third-party-advisory
Sources
- CVE List CVE-2017-14061
- NVD CVE-2017-14061
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.