ID CVE-2016-8638
Summary A vulnerability in ipsilon 2.0 before 2.0.2, 1.2 before 1.2.1, 1.1 before 1.1.2, and 1.0 before 1.0.3 was found that allows attacker to log out active sessions of other users. This issue is related to how it tracks sessions, and allows an unauthenticated attacker to view and terminate active sessions from other users. It is also called a "SAML2 multi-session vulnerability."
Vulnerable Configurations
  • cpe:2.3:a:ipsilon_project:ipsilon:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ipsilon_project:ipsilon:2.0.1:*:*:*:*:*:*:*
Base: 6.4 (as of 05-01-2018 - 02:31)
  • Manipulating Opaque Client-based Data Tokens
    In circumstances where an application holds important data client-side in tokens (cookies, URLs, data files, and so forth) that data can be manipulated. If client or server-side application components reinterpret that data as authentication tokens or data (such as store item pricing or wallet information) then even opaquely manipulating that data may bear fruit for an Attacker. In this pattern an attacker undermines the assumption that client side tokens have been adequately protected from tampering through use of encryption or obfuscation.
  • Session Fixation
    The attacker induces a client to establish a session with the target software using a session identifier provided by the attacker. Once the user successfully authenticates to the target software, the attacker uses the (now privileged) session identifier in their own transactions. This attack leverages the fact that the target software either relies on client-generated session identifiers or maintains the same session identifiers after privilege elevation.
  • Exploitation of Trusted Credentials
    Attacks on session IDs and resource IDs take advantage of the fact that some software accepts user input without verifying its authenticity. For example, a message queuing system that allows service requesters to post messages to its queue through an open channel (such as anonymous FTP), authorization is done through checking group or role membership contained in the posted message. However, there is no proof that the message itself, the information in the message (such group or role membership), or indeed the process that wrote the message to the queue are authentic and authorized to do so. Many server side processes are vulnerable to these attacks because the server to server communications have not been analyzed from a security perspective or the processes "trust" other systems because they are behind a firewall. In a similar way servers that use easy to guess or spoofable schemes for representing digital identity can also be vulnerable. Such systems frequently use schemes without cryptography and digital signatures (or with broken cryptography). Session IDs may be guessed due to insufficient randomness, poor protection (passed in the clear), lack of integrity (unsigned), or improperly correlation with access control policy enforcement points. Exposed configuration and properties files that contain system passwords, database connection strings, and such may also give an attacker an edge to identify these identifiers. The net result is that spoofing and impersonation is possible leading to an attacker's ability to break authentication, authorization, and audit controls on the system.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Session Credential Falsification through Forging
    An attacker creates a false but functional session credential in order to gain or usurp access to a service. Session credentials allow users to identify themselves to a service after an initial authentication without needing to resend the authentication information (usually a username and password) with every message. If an attacker is able to forge valid session credentials they may be able to bypass authentication or piggy-back off some other authenticated user's session. This attack differs from Reuse of Session IDs and Session Sidejacking attacks in that in the latter attacks an attacker uses a previous or existing credential without modification while, in a forging attack, the attacker must create their own credential, although it may be based on previously observed credentials.
  • Accessing/Intercepting/Modifying HTTP Cookies
    This attack relies on the use of HTTP Cookies to store credentials, state information and other critical data on client systems. There are several different forms of this attack. The first form of this attack involves accessing HTTP Cookies to mine for potentially sensitive data contained therein. The second form involves intercepting this data as it is transmitted from client to server. This intercepted information is then used by the adversary to impersonate the remote user/session. The third form is when the cookie's content is modified by the adversary before it is sent back to the server. Here the adversary seeks to convince the target server to operate on this falsified information.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
cvss-vector via4 AV:N/AC:L/Au:N/C:P/I:N/A:P
redhat via4
id 1392829
title CVE-2016-8638 ipsilon: DoS via logging out all open SAML2 sessions
  • comment Red Hat Enterprise Linux must be installed
    oval oval:com.redhat.rhba:tst:20070304026
  • AND
    • comment Red Hat Enterprise Linux 7 is installed
      oval oval:com.redhat.rhba:tst:20150364027
    • OR
      • AND
        • comment ipsilon is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809001
        • comment ipsilon is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809002
      • AND
        • comment ipsilon-authform is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809003
        • comment ipsilon-authform is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809004
      • AND
        • comment ipsilon-authgssapi is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809005
        • comment ipsilon-authgssapi is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809006
      • AND
        • comment ipsilon-authldap is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809007
        • comment ipsilon-authldap is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809008
      • AND
        • comment ipsilon-base is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809009
        • comment ipsilon-base is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809010
      • AND
        • comment ipsilon-client is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809011
        • comment ipsilon-client is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809012
      • AND
        • comment ipsilon-filesystem is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809013
        • comment ipsilon-filesystem is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809014
      • AND
        • comment ipsilon-infosssd is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809015
        • comment ipsilon-infosssd is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809016
      • AND
        • comment ipsilon-persona is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809017
        • comment ipsilon-persona is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809018
      • AND
        • comment ipsilon-saml2 is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809019
        • comment ipsilon-saml2 is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809020
      • AND
        • comment ipsilon-saml2-base is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809021
        • comment ipsilon-saml2-base is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809022
      • AND
        • comment ipsilon-tools-ipa is earlier than 0:1.0.0-13.el7_3
          oval oval:com.redhat.rhsa:tst:20162809023
        • comment ipsilon-tools-ipa is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162809024
id RHSA-2016:2809
released 2016-11-21
severity Important
title RHSA-2016:2809: ipsilon security update (Important)
  • ipsilon-0:1.0.0-13.el7_3
  • ipsilon-authform-0:1.0.0-13.el7_3
  • ipsilon-authgssapi-0:1.0.0-13.el7_3
  • ipsilon-authldap-0:1.0.0-13.el7_3
  • ipsilon-base-0:1.0.0-13.el7_3
  • ipsilon-client-0:1.0.0-13.el7_3
  • ipsilon-filesystem-0:1.0.0-13.el7_3
  • ipsilon-infosssd-0:1.0.0-13.el7_3
  • ipsilon-persona-0:1.0.0-13.el7_3
  • ipsilon-saml2-0:1.0.0-13.el7_3
  • ipsilon-saml2-base-0:1.0.0-13.el7_3
  • ipsilon-tools-ipa-0:1.0.0-13.el7_3
refmap via4
bid 94439
Last major update 05-01-2018 - 02:31
Published 12-07-2017 - 13:29
Last modified 05-01-2018 - 02:31
Back to Top