CVE-2015-5179 json
FreeIPA might display user data improperly via vectors involving non-printable characters.
published 9y ago modified 4mo ago also EUVD-2015-5180
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
FreeIPA might display user data improperly via vectors involving non-printable characters.
Is CVE-2015-5179 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-2015-5179 updated cvss 4.0
FreeIPA: non-printable characters aren't checked in every case of user data
-
Red Hat Enterprise Linux 6 ipa, ipa-client, ipa-python, ipa-server, ipa-admintools, ipa-server-selinux, +1 more Red Hat Enterprise Linux 7 ipa, ipa-client, ipa-common, ipa-python, ipa-server, ipa-admintools, +8 moreunder investigation
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
1.07% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- pagure.io https://pagure.io/freeipa/issue/5153 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
pagure.io
/freeipa/issue/5153
exploit, issue-tracking, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1252567
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2015-5179
- NVD CVE-2015-5179
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.