IBM WebSphere Message Broker 6.1.0.1

CPE Details

IBM WebSphere Message Broker 6.1.0.1
6.1.0.1
2009-02-16
12h08 +00:00
2009-02-16
12h08 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:ibm:websphere_message_broker:6.1.0.1:*:*:*:*:*:*:*

Informations

Vendor

ibm

Product

websphere_message_broker

Version

6.1.0.1

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2013-5372 2013-10-19 08h00 +00:00 The XML4J parser in IBM WebSphere Message Broker 6.1 before 6.1.0.12, 7.0 before 7.0.0.7, and 8.0 before 8.0.0.4 and IBM Integration Bus 9.0 before 9.0.0.1 allows remote attackers to cause a denial of service (memory consumption) via a crafted XML document that triggers expansion for many entities.
4.3
CVE-2012-5952 2013-02-20 10h00 +00:00 IBM WebSphere Message Broker 6.1 before 6.1.0.12, 7.0 before 7.0.0.6, and 8.0 before 8.0.0.2 does not validate Basic Authentication credentials before proceeding to WS-Addressing and WS-Security operations, which allows remote attackers to trigger transmission of unauthenticated messages via unspecified vectors.
5
CVE-2012-5953 2013-02-20 10h00 +00:00 IBM WebSphere Message Broker 6.1 before 6.1.0.12, 7.0 before 7.0.0.6, and 8.0 before 8.0.0.2, when the Parse Query Strings option is enabled on an HTTPInput node, allows remote attackers to cause a denial of service (infinite loop) via a crafted query string.
4.3
CVE-2012-3317 2012-12-05 10h00 +00:00 IBM WebSphere Message Broker 6.1 before 6.1.0.11, 7.0 before 7.0.0.5, and 8.0 before 8.0.0.2 has incorrect ownership of certain uninstaller Java Runtime Environment (JRE) files, which might allow local users to gain privileges by leveraging access to uid 501 or gid 300.
6.9
CVE-2009-0503 2009-02-13 16h00 +00:00 IBM WebSphere Message Broker 6.1.x before 6.1.0.2 writes a database connection password to the Event Log and System Log during exception handling for a JDBC error, which allows local users to obtain sensitive information by reading these logs.
2.1