ID CVE-2011-1411
Summary Shibboleth OpenSAML library 2.4.x before 2.4.3 and 2.5.x before 2.5.1, and IdP before 2.3.2, allows remote attackers to forge messages and bypass authentication via an "XML Signature wrapping attack."
References
Vulnerable Configurations
  • cpe:2.3:a:shibboleth:opensaml:2.4.0
    cpe:2.3:a:shibboleth:opensaml:2.4.0
  • cpe:2.3:a:shibboleth:opensaml:2.4.1
    cpe:2.3:a:shibboleth:opensaml:2.4.1
  • cpe:2.3:a:shibboleth:opensaml:2.4.2
    cpe:2.3:a:shibboleth:opensaml:2.4.2
  • cpe:2.3:a:shibboleth:opensaml:2.5.0
    cpe:2.3:a:shibboleth:opensaml:2.5.0
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.3.1
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.3.1
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.3.0
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.3.0
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.2.1
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.2.1
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.2.0
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.2.0
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.5
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.5
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.4
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.4
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.3
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.3
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.2
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.2
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.1
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.1
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.0
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.1.0
  • cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.0.0
    cpe:2.3:a:shibboleth:shibboleth-identity-provider:2.0.0
CVSS
Base: 5.8 (as of 05-09-2011 - 12:38)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL NONE
nessus via4
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2284.NASL
    description Juraj Somorovsky, Andreas Mayer, Meiko Jensen, Florian Kohlar, Marco Kampmann and Joerg Schwenk discovered that Shibboleth, a federated web single sign-on system is vulnerable to XML signature wrapping attacks. More details can be found in the Shibboleth advisory.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 55674
    published 2011-07-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=55674
    title Debian DSA-2284-1 : opensaml2 - implementation error
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2011-12890.NASL
    description Backport of 2.4.3 patch which fixes CVE-2011-1411. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2016-05-11
    plugin id 56303
    published 2011-09-27
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=56303
    title Fedora 15 : opensaml-2.3-4.fc15 (2011-12890)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2011-12815.NASL
    description Backport of 2.4.3 patch which fixes CVE-2011-1411. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2016-05-11
    plugin id 56360
    published 2011-10-03
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=56360
    title Fedora 16 : opensaml-2.3-6.fc16 (2011-12815)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_9F14CB36B6FC11E0A044445C73746D79.NASL
    description OpenSAML developer reports : The Shibboleth software relies on the OpenSAML libraries to perform verification of signed XML messages such as attribute queries or SAML assertions. Both the Java and C++ versions are vulnerable to a so-called 'wrapping attack' that allows a remote, unauthenticated attacker to craft specially formed messages that can be successfully verified, but contain arbitrary content.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 55681
    published 2011-07-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=55681
    title FreeBSD : opensaml2 -- unauthenticated login (9f14cb36-b6fc-11e0-a044-445c73746d79)
  • NASL family Web Servers
    NASL id WEBSPHERE_7_0_0_19.NASL
    description IBM WebSphere Application Server 7.0 before Fix Pack 19 appears to be running on the remote host. As such, it is potentially affected by the following vulnerabilities : - An open redirect vulnerability exists related to the 'logoutExitPage' parameter. This can allow remote attackers to trick users into requesting unintended URLs. (PM35701) - The administrative console can display a stack trace under unspecified circumstances and can disclose potentially sensitive information to local users. (PM36620) - The Installation Verification Tool servlet (IVT) does not properly sanitize user-supplied input of arbitrary HTML and script code, which could allow cross-site scripting attacks. (PM40733) - A token verification error exists in the bundled OpenSAML library. This error can allow an attacker to bypass security controls with an XML signature wrapping attack via SOAP messages. (PM43254) - A directory traversal attack is possible via unspecified parameters in the 'help' servlet. (PM45322)
    last seen 2019-02-21
    modified 2018-08-06
    plugin id 56229
    published 2011-09-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=56229
    title IBM WebSphere Application Server 7.0 < Fix Pack 19 Multiple Vulnerabilities
  • NASL family Web Servers
    NASL id WEBSPHERE_8_0_0_1.NASL
    description IBM WebSphere Application Server 8.0 before Fix Pack 1 appears to be running on the remote host and is potentially affected by the following vulnerabilities : - An open redirect vulnerability exists related to the 'logoutExitPage' parameter. This can allow remote attackers to trick users into requesting unintended URLs. (PM35701) - The administrative console can display a stack trace under unspecified circumstances and can disclose potentially sensitive information to local users. (PM36620) - An unspecified error exists that can allow cross-site request forgery attacks. (PM36734) - A token verification error exists in the bundled OpenSAML library. This error can allow an attacker to bypass security controls with an XML signature wrapping attack via SOAP messages. (PM43254) - A directory traversal attack is possible via unspecified parameters in the 'help' servlet. (PM45322) - The JavaServer Faces (JSF) application functionality could allow a remote attacker to read files because it fails to properly handle requests. (PM45992) - The HTTP server contains an error in the 'ByteRange' filter and can allow denial of service attacks when processing malicious requests. (PM46234)
    last seen 2019-02-21
    modified 2018-11-15
    plugin id 56348
    published 2011-09-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=56348
    title IBM WebSphere Application Server 8.0 < Fix Pack 1 Multiple Vulnerabilities
refmap via4
confirm
debian DSA-2284
mandriva MDVSA-2013:150
secunia 50994
Last major update 10-10-2013 - 23:34
Published 02-09-2011 - 19:55
Back to Top