FedoraOperating system · Fedoraproject
CVE-2015-1827
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe get_user_grouplist function in the extdom plug-in in FreeIPA before 4.1.4 does not properly reallocate memory when processing user accounts, which allows remote attackers to cause a denial of service (crash) via a group list request for a user that belongs to a large number of groups.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe get_user_grouplist function in FreeIPA's extdom plug-in has a memory allocation flaw. When processing users belonging to many groups, the function fails to properly reallocate memory buffers, causing a crash. Remote attackers can trigger this by requesting group lists for users with extensive group memberships.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FedoraOperating system
= 21= 22<= 4.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if FreeIPA is installedQuery the installed FreeIPA package version using the system package manager (e.g., rpm -qa freeipa or dpkg -l freeipa)Affected if FreeIPA is not installed or no version information is returned, then the system is not affected by this specific vulnerability in FreeIPA
-
Verify FreeIPA versionCompare the installed FreeIPA version against the affected range: versions 4.1.3 and earlier on Fedora 21/22 or any platformAffected if Installed version is 4.1.3 or earlier, indicating the vulnerable code is present
-
Confirm extdom plug-in is in useCheck if the extdom plug-in is loaded and active in the FreeIPA directory server configuration (e.g., inspect dsctl or directory server plugin status)Affected if The extdom plug-in is enabled and processing user group lookups, which is required to trigger the flaw
-
Identify users with extensive group membershipsQuery directory user entries to find accounts belonging to a large number of groups (e.g., using ldapsearch or ipa user-show with group membership enumeration)Affected if Users exist with group memberships exceeding typical thresholds, creating conditions for the memory reallocation failure to occur during get_user_grouplist execution
The environment is affected if FreeIPA version 4.1.3 or earlier is installed with the extdom plug-in enabled and users possessing extensive group memberships are present, allowing the memory buffer reallocation flaw to trigger during group list requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade FreeIPA to version 4.1.4 or later, which contains the corrected memory management logic in the extdom plug-in.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1827 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-1827 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data