dbcve.org
FreeipaApplication · Redhat

CVE-2011-3636

MEDIUM · 6.8 CVSS v2.0 Published 2011-12-08
Fix available
A fix is available. Upgrade to after 2.1.3 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Cross-site request forgery (CSRF) vulnerability in the management interface in FreeIPA before 2.1.4 allows remote attackers to hijack the authentication of administrators for requests that make configuration changes.

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 · high confidence

Cross-site request forgery (CSRF) vulnerability in FreeIPA's admin web interface allows remote attackers to trick authenticated administrators into making unauthorized configuration changes by forging malicious requests.

MitigationUpgrade to FreeIPA 2.1.4 or later which includes CSRF protection mechanisms, or implement anti-CSRF tokens in the management interface if patching is not feasible.

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
FreeipaApplication
Affected:<= 2.1.3= 0.99= 0.99698-20080228= 0.99698641-20080218= 1.0.0= 1.1.0= 1.1.1= 1.2.0= 1.2.1= 1.2.2= 1.9.0= 2.0.0

CVSS 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed FreeIPA version
    Run 'ipa --version' or check the package version using 'rpm -q freeipa-server'
    Affected if The installed version is 2.1.3 or earlier, or matches any of these specific versions: 0.99, 0.99698-20080228, 0.99698641-20080218, 1.0.0, 1.1.0, 1.1.1, 1.2.0, 1.2.1, 1.2.2, 1.9.0, or 2.0.0
  2. Confirm the FreeIPA admin web interface is enabled
    Check if the Apache service (httpd) is running and configured for FreeIPA, or verify the web UI port is accessible
    Affected if The admin web interface (typically port 443 or 8443) is exposed and accessible to users
  3. Verify the web interface lacks CSRF protection
    Inspect web requests and responses from the admin interface for the presence of anti-CSRF tokens or referer validation headers
    Affected if No CSRF tokens are present in admin web forms and no referer/origin header validation is performed on configuration change requests

The environment is affected if FreeIPA version 2.1.3 or earlier (or one of the specific affected versions) is installed AND the admin web interface is accessible and lacks CSRF protection mechanisms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.1.3
Interim mitigation

Upgrade to FreeIPA 2.1.4 or later which includes CSRF protection mechanisms, or implement anti-CSRF tokens in the management interface if patching is not feasible.

Fix this in Freeipa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3636 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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