ID CVE-2011-3636
Summary 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.
References
Vulnerable Configurations
  • cpe:2.3:a:redhat:freeipa:1.1.0
    cpe:2.3:a:redhat:freeipa:1.1.0
  • cpe:2.3:a:redhat:freeipa:1.0.0
    cpe:2.3:a:redhat:freeipa:1.0.0
  • cpe:2.3:a:redhat:freeipa:0.99
    cpe:2.3:a:redhat:freeipa:0.99
  • Red Hat FreeIPA 2.1.3
    cpe:2.3:a:redhat:freeipa:2.1.3
  • cpe:2.3:a:redhat:freeipa:2.1.2
    cpe:2.3:a:redhat:freeipa:2.1.2
  • Red Hat FreeIPA 2.1.1
    cpe:2.3:a:redhat:freeipa:2.1.1
  • Red Hat FreeIPA 2.1.0
    cpe:2.3:a:redhat:freeipa:2.1.0
  • Red Hat FreeIPA 2.0.1
    cpe:2.3:a:redhat:freeipa:2.0.1
  • Red Hat FreeIPA 2.0.0
    cpe:2.3:a:redhat:freeipa:2.0.0
  • cpe:2.3:a:redhat:freeipa:2.0.0:rc3
    cpe:2.3:a:redhat:freeipa:2.0.0:rc3
  • cpe:2.3:a:redhat:freeipa:2.0.0:rc2
    cpe:2.3:a:redhat:freeipa:2.0.0:rc2
  • cpe:2.3:a:redhat:freeipa:2.0.0:rc1
    cpe:2.3:a:redhat:freeipa:2.0.0:rc1
  • cpe:2.3:a:redhat:freeipa:2.0.0:pre2
    cpe:2.3:a:redhat:freeipa:2.0.0:pre2
  • cpe:2.3:a:redhat:freeipa:2.0.0:pre1
    cpe:2.3:a:redhat:freeipa:2.0.0:pre1
  • cpe:2.3:a:redhat:freeipa:1.9.0:pre5
    cpe:2.3:a:redhat:freeipa:1.9.0:pre5
  • cpe:2.3:a:redhat:freeipa:1.9.0:pre4
    cpe:2.3:a:redhat:freeipa:1.9.0:pre4
  • cpe:2.3:a:redhat:freeipa:1.9.0:pre3
    cpe:2.3:a:redhat:freeipa:1.9.0:pre3
  • cpe:2.3:a:redhat:freeipa:1.9.0:pre2
    cpe:2.3:a:redhat:freeipa:1.9.0:pre2
  • cpe:2.3:a:redhat:freeipa:1.9.0:pre1
    cpe:2.3:a:redhat:freeipa:1.9.0:pre1
  • cpe:2.3:a:redhat:freeipa:1.2.2
    cpe:2.3:a:redhat:freeipa:1.2.2
  • cpe:2.3:a:redhat:freeipa:1.2.1
    cpe:2.3:a:redhat:freeipa:1.2.1
  • cpe:2.3:a:redhat:freeipa:1.2.0
    cpe:2.3:a:redhat:freeipa:1.2.0
  • cpe:2.3:a:redhat:freeipa:1.1.1
    cpe:2.3:a:redhat:freeipa:1.1.1
  • cpe:2.3:a:redhat:freeipa:1.0.0:b
    cpe:2.3:a:redhat:freeipa:1.0.0:b
  • cpe:2.3:a:redhat:freeipa:1.0.0:a
    cpe:2.3:a:redhat:freeipa:1.0.0:a
  • cpe:2.3:a:redhat:freeipa:0.99698-20080228
    cpe:2.3:a:redhat:freeipa:0.99698-20080228
  • cpe:2.3:a:redhat:freeipa:0.99698641-20080218
    cpe:2.3:a:redhat:freeipa:0.99698641-20080218
CVSS
Base: 6.8 (as of 08-12-2011 - 16:58)
Impact:
Exploitability:
CWE CWE-352
CAPEC
  • JSON Hijacking (aka JavaScript Hijacking)
    An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. An attacker gets the victim to visit his or her malicious page that contains a script tag whose source points to the vulnerable system with a URL that requests a response from the server containing a JSON object with possibly confidential information. The malicious page also contains malicious code to capture the JSON object returned by the server before any other processing on it can take place, typically by overriding the JavaScript function used to create new objects. This hook allows the malicious code to get access to the creation of each object and transmit the possibly sensitive contents of the captured JSON object to the attackers' server. There is nothing in the browser's security model to prevent the attackers' malicious JavaScript code (originating from attacker's domain) to set up an environment (as described above) to intercept a JSON object response (coming from the vulnerable target system's domain), read its contents and transmit to the attackers' controlled site. The same origin policy protects the domain object model (DOM), but not the JSON.
  • Cross-Domain Search Timing
    An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain. For GET requests an attacker could for instance leverage the "img" tag in conjunction with "onload() / onerror()" javascript events. For the POST requests, an attacker could leverage the "iframe" element and leverage the "onload()" event. There is nothing in the current browser security model that prevents an attacker to use these methods to time responses to the attackers' cross domain requests. The timing for these responses leaks information. For instance, if a victim has an active session with their online e-mail account, an attacker could issue search requests in the victim's mailbox. While the attacker is not able to view the responses, based on the timings of the responses, the attacker could ask yes / no questions as to the content of victim's e-mails, who the victim e-mailed, when, etc. This is but one example; There are other scenarios where an attacker could infer potentially sensitive information from cross domain requests by timing the responses while asking the right questions that leak information.
  • Cross Site Identification
    An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the "remember me" feature to keep his or her session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing). In one example of an attack, an attacker may post a malicious posting that contains an image with an embedded link. The link actually requests identifying information from the social networking site. A victim who views the malicious posting in his or her browser will have sent identifying information to the attacker, as long as the victim had an active session with the social networking site. There are many other ways in which the attacker may get the payload to execute in the victim's browser mainly by finding a way to hide it in some reputable site that the victim visits. The attacker could also send the link to the victim in an e-mail and trick the victim into clicking on the link. This attack is basically a cross site request forgery attack with two main differences. First, there is no action that is performed on behalf of the user aside from harvesting information. So standard CSRF protection may not work in this situation. Second, what is important in this attack pattern is the nature of the data being harvested, which is identifying information that can be obtained and used in context. This real time harvesting of identifying information can be used as a prelude for launching real time targeted social engineering attacks on the victim.
  • Cross Site Request Forgery (aka Session Riding)
    An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20111206_IPA_ON_SL6_X.NASL
    description This Identity Management Application is a centralized authentication, identity management and authorization solution for both traditional and cloud based enterprise environments. It integrates components of the Upstream Directory Server, MIT Kerberos, the Upstream Certificate System, NTP, and DNS. It provides web browser and command-line interfaces. Its administration tools allow an administrator to quickly install, set up, and administer a group of domain controllers to meet the authentication and identity management requirements of large scale Linux and UNIX deployments. A Cross-Site Request Forgery (CSRF) flaw was found in this package. If a remote attacker could trick a user, who was logged into the management web interface, into visiting a specially crafted URL, the attacker could perform configuration changes with the privileges of the logged in user. (CVE-2011-3636) Due to the changes required to fix CVE-2011-3636, client tools will need to be updated for client systems to communicate with updated servers. New client systems will need to have the updated ipa-client package installed to be enrolled. Already enrolled client systems will need to have the updated certmonger package installed to be able to renew their system certificate. Note that system certificates are valid for two years by default. This update includes several bug fixes. Space precludes documenting all of these changes in this advisory. Users of this software should upgrade to these updated packages, which correct these issues. A number of additional packages were added to the security repository so that this package could be installed on older SL systems.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 61188
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=61188
    title Scientific Linux Security Update : ipa on SL6.x i386/x86_64
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2011-1533.NASL
    description Updated ipa packages that fix one security issue and several bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. Red Hat Identity Management is a centralized authentication, identity management and authorization solution for both traditional and cloud based enterprise environments. It integrates components of the Red Hat Directory Server, MIT Kerberos, Red Hat Certificate System, NTP and DNS. It provides web browser and command-line interfaces. Its administration tools allow an administrator to quickly install, set up, and administer a group of domain controllers to meet the authentication and identity management requirements of large scale Linux and UNIX deployments. A Cross-Site Request Forgery (CSRF) flaw was found in Red Hat Identity Management. If a remote attacker could trick a user, who was logged into the management web interface, into visiting a specially crafted URL, the attacker could perform Red Hat Identity Management configuration changes with the privileges of the logged in user. (CVE-2011-3636) Due to the changes required to fix CVE-2011-3636, client tools will need to be updated for client systems to communicate with updated Red Hat Identity Management servers. New client systems will need to have the updated ipa-client package installed to be enrolled. Already enrolled client systems will need to have the updated certmonger package installed to be able to renew their system certificate. Note that system certificates are valid for two years by default. Updated ipa-client and certmonger packages for Red Hat Enterprise Linux 6 were released as part of Red Hat Enterprise Linux 6.2. Future updates will provide updated packages for Red Hat Enterprise Linux 5. This update includes several bug fixes. Space precludes documenting all of these changes in this advisory. Users are directed to the Red Hat Enterprise Linux 6.2 Technical Notes for information on the most significant of these changes, linked to in the References section. Users of Red Hat Identity Management should upgrade to these updated packages, which correct these issues.
    last seen 2019-02-21
    modified 2018-12-20
    plugin id 57014
    published 2011-12-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=57014
    title RHEL 6 : ipa (RHSA-2011:1533)
redhat via4
advisories
bugzilla
id 751179
title [ipa webui] Unable to change password, misleading error
oval
AND
  • OR
    • comment Red Hat Enterprise Linux 6 Client is installed
      oval oval:com.redhat.rhsa:tst:20100842001
    • comment Red Hat Enterprise Linux 6 Server is installed
      oval oval:com.redhat.rhsa:tst:20100842002
    • comment Red Hat Enterprise Linux 6 Workstation is installed
      oval oval:com.redhat.rhsa:tst:20100842003
    • comment Red Hat Enterprise Linux 6 ComputeNode is installed
      oval oval:com.redhat.rhsa:tst:20100842004
  • OR
    • AND
      • comment ipa-admintools is earlier than 0:2.1.3-9.el6
        oval oval:com.redhat.rhsa:tst:20111533005
      • comment ipa-admintools is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20111533006
    • AND
      • comment ipa-client is earlier than 0:2.1.3-9.el6
        oval oval:com.redhat.rhsa:tst:20111533009
      • comment ipa-client is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20111533010
    • AND
      • comment ipa-python is earlier than 0:2.1.3-9.el6
        oval oval:com.redhat.rhsa:tst:20111533007
      • comment ipa-python is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20111533008
    • AND
      • comment ipa-server is earlier than 0:2.1.3-9.el6
        oval oval:com.redhat.rhsa:tst:20111533011
      • comment ipa-server is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20111533012
    • AND
      • comment ipa-server-selinux is earlier than 0:2.1.3-9.el6
        oval oval:com.redhat.rhsa:tst:20111533013
      • comment ipa-server-selinux is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20111533014
rhsa
id RHSA-2011:1533
released 2011-12-06
severity Moderate
title RHSA-2011:1533: ipa security and bug fix update (Moderate)
rpms
  • ipa-admintools-0:2.1.3-9.el6
  • ipa-client-0:2.1.3-9.el6
  • ipa-python-0:2.1.3-9.el6
  • ipa-server-0:2.1.3-9.el6
  • ipa-server-selinux-0:2.1.3-9.el6
refmap via4
confirm http://freeipa.org/page/IPAv2_214
Last major update 05-03-2012 - 00:00
Published 08-12-2011 - 06:55
Back to Top