Vulnerabilities > CVE-2014-0034 - Improper Input Validation vulnerability in multiple products

047910
CVSS 0.0 - NONE
Attack vector
UNKNOWN
Attack complexity
UNKNOWN
Privileges required
UNKNOWN
Confidentiality impact
UNKNOWN
Integrity impact
UNKNOWN
Availability impact
UNKNOWN

Summary

The SecurityTokenService (STS) in Apache CXF before 2.6.12 and 2.7.x before 2.7.9 does not properly validate SAML tokens when caching is enabled, which allows remote attackers to gain access via an invalid SAML token.

Vulnerable Configurations

Part Description Count
Application
Apache
88
Application
Redhat
2

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Server Side Include (SSI) Injection
    An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands.
  • Cross Zone Scripting
    An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. In a zone-based model, pages belong to one of a set of zones corresponding to the level of privilege assigned to that page. Pages in an untrusted zone would have a lesser level of access to the system and/or be restricted in the types of executable content it was allowed to invoke. In a cross-zone scripting attack, a page that should be assigned to a less privileged zone is granted the privileges of a more trusted zone. This can be accomplished by exploiting bugs in the browser, exploiting incorrect configuration in the zone controls, through a cross-site scripting attack that causes the attackers' content to be treated as coming from a more trusted page, or by leveraging some piece of system functionality that is accessible from both the trusted and less trusted zone. This attack differs from "Restful Privilege Escalation" in that the latter correlates to the inadequate securing of RESTful access methods (such as HTTP DELETE) on the server, while cross-zone scripting attacks the concept of security zones as implemented by a browser.
  • Cross Site Scripting through Log Files
    An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.

Nessus

  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2014-0798.NASL
    descriptionUpdated packages that provide Red Hat JBoss Enterprise Application Platform 6.2.4 and fix multiple security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Red Hat JBoss Enterprise Application Platform 6 is a platform for Java applications based on JBoss Application Server 7. Apache CXF is an open source services framework, which is a part of Red Hat JBoss Enterprise Application Platform. It was found that the SecurityTokenService (STS), provided as a part of Apache CXF, could under certain circumstances accept invalid SAML tokens as valid. A remote attacker could use a specially crafted SAML token to gain access to an application that uses STS for validation of SAML tokens. (CVE-2014-0034) A denial of service flaw was found in the way Apache CXF created error messages for certain POST requests. A remote attacker could send a specially crafted request which, when processed by an application using Apache CXF, could consume an excessive amount of memory on the system, possibly triggering an Out Of Memory (OOM) error. (CVE-2014-0109) It was found that when a large invalid SOAP message was processed by Apache CXF, it could be saved to a temporary file in the /tmp directory. A remote attacker could send a specially crafted SOAP message that, when processed by an application using Apache CXF, would use an excessive amount of disk space, possibly causing a denial of service. (CVE-2014-0110) It was found that the Java API for RESTful Web Services (JAX-RS) implementation enabled external entity expansion by default. A remote attacker could use this flaw to view the contents of arbitrary files accessible to the application server user. (CVE-2014-3481) It was discovered that UsernameTokens were sent in plain text by an Apache CXF client that used a Symmetric EncryptBeforeSigning password policy. A man-in-the-middle attacker could use this flaw to obtain the user name and password used by the client application using Apache CXF. (CVE-2014-0035) The CVE-2014-3481 issue was discovered by the Red Hat JBoss Enterprise Application Platform QE team. This release serves as a replacement for Red Hat JBoss Enterprise Application Platform 6.2.3, and includes bug fixes and enhancements. Documentation for these changes will be available shortly from the Red Hat JBoss Enterprise Application Platform 6.2.4 Release Notes, linked to in the References. All users of Red Hat JBoss Enterprise Application Platform 6.2 on Red Hat Enterprise Linux 5 are advised to upgrade to these updated packages. The JBoss server process must be restarted for the update to take effect.
    last seen2020-06-01
    modified2020-06-02
    plugin id76292
    published2014-06-28
    reporterThis script is Copyright (C) 2014-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/76292
    titleRHEL 5 : JBoss EAP (RHSA-2014:0798)
  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2014-0799.NASL
    descriptionUpdated packages that provide Red Hat JBoss Enterprise Application Platform 6.2.4 and fix multiple security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Red Hat JBoss Enterprise Application Platform 6 is a platform for Java applications based on JBoss Application Server 7. Apache CXF is an open source services framework, which is a part of Red Hat JBoss Enterprise Application Platform. It was found that the SecurityTokenService (STS), provided as a part of Apache CXF, could under certain circumstances accept invalid SAML tokens as valid. A remote attacker could use a specially crafted SAML token to gain access to an application that uses STS for validation of SAML tokens. (CVE-2014-0034) A denial of service flaw was found in the way Apache CXF created error messages for certain POST requests. A remote attacker could send a specially crafted request which, when processed by an application using Apache CXF, could consume an excessive amount of memory on the system, possibly triggering an Out Of Memory (OOM) error. (CVE-2014-0109) It was found that when a large invalid SOAP message was processed by Apache CXF, it could be saved to a temporary file in the /tmp directory. A remote attacker could send a specially crafted SOAP message that, when processed by an application using Apache CXF, would use an excessive amount of disk space, possibly causing a denial of service. (CVE-2014-0110) It was found that the Java API for RESTful Web Services (JAX-RS) implementation enabled external entity expansion by default. A remote attacker could use this flaw to view the contents of arbitrary files accessible to the application server user. (CVE-2014-3481) It was discovered that UsernameTokens were sent in plain text by an Apache CXF client that used a Symmetric EncryptBeforeSigning password policy. A man-in-the-middle attacker could use this flaw to obtain the user name and password used by the client application using Apache CXF. (CVE-2014-0035) The CVE-2014-3481 issue was discovered by the Red Hat JBoss Enterprise Application Platform QE team. This release serves as a replacement for Red Hat JBoss Enterprise Application Platform 6.2.3, and includes bug fixes and enhancements. Documentation for these changes will be available shortly from the Red Hat JBoss Enterprise Application Platform 6.2.4 Release Notes, linked to in the References. All users of Red Hat JBoss Enterprise Application Platform 6.2 on Red Hat Enterprise Linux 6 are advised to upgrade to these updated packages. The JBoss server process must be restarted for the update to take effect.
    last seen2020-06-01
    modified2020-06-02
    plugin id76293
    published2014-06-28
    reporterThis script is Copyright (C) 2014-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/76293
    titleRHEL 6 : JBoss EAP (RHSA-2014:0799)
  • NASL familyFedora Local Security Checks
    NASL idFEDORA_2015-4726.NASL
    descriptionCXF upgrade to 2.7.11. 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 seen2020-06-05
    modified2015-04-22
    plugin id82944
    published2015-04-22
    reporterThis script is Copyright (C) 2015-2020 Tenable Network Security, Inc.
    sourcehttps://www.tenable.com/plugins/nessus/82944
    titleFedora 22 : cxf-2.7.11-1.fc22 / cxf-build-utils-2.6.0-1.fc22 / cxf-xjc-utils-2.6.2-1.fc22 / etc (2015-4726)

Redhat

advisories
  • rhsa
    idRHSA-2014:0797
  • rhsa
    idRHSA-2014:0798
  • rhsa
    idRHSA-2014:0799
  • rhsa
    idRHSA-2014:1351
  • rhsa
    idRHSA-2015:0850
  • rhsa
    idRHSA-2015:0851
rpms
  • apache-cxf-0:2.7.11-3.redhat_3.1.ep6.el5
  • hibernate4-core-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el5
  • hibernate4-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el5
  • hibernate4-entitymanager-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el5
  • hibernate4-envers-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el5
  • hibernate4-infinispan-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el5
  • jboss-aesh-0:0.33.12-1.redhat_1.1.ep6.el5
  • jboss-as-appclient-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-cli-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-client-all-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-clustering-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-cmp-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-configadmin-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-connector-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-controller-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-controller-client-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-core-security-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-deployment-repository-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-deployment-scanner-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-domain-http-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-domain-management-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-ee-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-ee-deployment-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-ejb3-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-embedded-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-host-controller-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jacorb-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jaxr-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jaxrs-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jdr-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jmx-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jpa-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jsf-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-jsr77-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-logging-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-mail-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-management-client-content-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-messaging-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-modcluster-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-naming-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-network-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-osgi-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-osgi-configadmin-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-osgi-service-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-platform-mbean-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-pojo-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-process-controller-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-protocol-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-remoting-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-sar-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-security-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-server-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-system-jmx-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-threads-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-transactions-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-version-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-web-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-webservices-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-weld-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-as-xts-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jboss-security-negotiation-0:2.2.10-1.Final_redhat_1.1.ep6.el5
  • jboss-xnio-base-0:3.0.10-1.GA_redhat_1.1.ep6.el5
  • jbossas-appclient-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-bundles-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-core-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-domain-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-javadocs-0:7.3.4-1.Final_redhat_1.ep6.el5
  • jbossas-modules-eap-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-product-eap-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-standalone-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossas-welcome-content-eap-0:7.3.4-1.Final_redhat_1.1.ep6.el5
  • jbossts-1:4.17.15-5.Final_redhat_5.1.ep6.el5
  • jbossweb-0:7.3.2-1.Final_redhat_1.1.ep6.el5
  • picketbox-0:4.0.19-8.SP8_redhat_1.1.ep6.el5
  • resteasy-0:2.3.7.2-1.Final_redhat_1.1.ep6.el5
  • weld-core-0:1.1.17-4.SP3_redhat_1.1.ep6.el5
  • wss4j-0:1.6.15-1.redhat_1.1.ep6.el5
  • apache-cxf-0:2.7.11-3.redhat_3.1.ep6.el6
  • hibernate4-core-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el6
  • hibernate4-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el6
  • hibernate4-entitymanager-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el6
  • hibernate4-envers-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el6
  • hibernate4-infinispan-eap6-0:4.2.7-9.SP5_redhat_1.1.ep6.el6
  • jboss-aesh-0:0.33.12-1.redhat_1.1.ep6.el6
  • jboss-as-appclient-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-cli-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-client-all-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-clustering-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-cmp-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-configadmin-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-connector-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-controller-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-controller-client-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-core-security-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-deployment-repository-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-deployment-scanner-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-domain-http-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-domain-management-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-ee-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-ee-deployment-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-ejb3-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-embedded-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-host-controller-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jacorb-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jaxr-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jaxrs-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jdr-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jmx-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jpa-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jsf-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-jsr77-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-logging-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-mail-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-management-client-content-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-messaging-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-modcluster-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-naming-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-network-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-osgi-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-osgi-configadmin-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-osgi-service-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-platform-mbean-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-pojo-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-process-controller-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-protocol-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-remoting-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-sar-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-security-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-server-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-system-jmx-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-threads-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-transactions-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-version-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-web-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-webservices-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-weld-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-as-xts-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jboss-security-negotiation-0:2.2.10-1.Final_redhat_1.1.ep6.el6
  • jboss-xnio-base-0:3.0.10-1.GA_redhat_1.1.ep6.el6
  • jbossas-appclient-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-bundles-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-core-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-domain-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-javadocs-0:7.3.4-1.Final_redhat_1.ep6.el6
  • jbossas-modules-eap-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-product-eap-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-standalone-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossas-welcome-content-eap-0:7.3.4-1.Final_redhat_1.1.ep6.el6
  • jbossts-1:4.17.15-5.Final_redhat_5.1.ep6.el6
  • jbossweb-0:7.3.2-1.Final_redhat_1.1.ep6.el6
  • picketbox-0:4.0.19-8.SP8_redhat_1.1.ep6.el6
  • resteasy-0:2.3.7.2-1.Final_redhat_1.1.ep6.el6
  • weld-core-0:1.1.17-4.SP3_redhat_1.1.ep6.el6
  • wss4j-0:1.6.15-1.redhat_1.1.ep6.el6