Vulnerabilities > CVE-2014-3481 - Information Exposure vulnerability in Redhat Jboss Enterprise Application Platform

047910
CVSS 5.0 - MEDIUM
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
NONE
Confidentiality impact
PARTIAL
Integrity impact
NONE
Availability impact
NONE
network
low complexity
redhat
CWE-200
nessus

Summary

org.jboss.as.jaxrs.deployment.JaxrsIntegrationProcessor in Red Hat JBoss Enterprise Application Platform (JEAP) before 6.2.4 enables entity expansion, which allows remote attackers to read arbitrary files via unspecified vectors, related to an XML External Entity (XXE) issue.

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • 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.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • 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.

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)

Redhat

advisories
  • rhsa
    idRHSA-2014:0797
  • rhsa
    idRHSA-2014:0798
  • rhsa
    idRHSA-2014:0799
  • rhsa
    idRHSA-2015:0675
  • rhsa
    idRHSA-2015:0720
  • rhsa
    idRHSA-2015:0765
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