lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date: Mon, 26 Jan 2015 09:10:47 +0000
From: Gordon Sim <gsim@...che.org>
To: "users@...d.apache.org" <users@...d.apache.org>,
  "dev@...d.apache.org" <dev@...d.apache.org>, announce@...che.org,
  "security@...che.org" <security@...che.org>, bugtraq@...urityfocus.com
Subject: CVE-2015-0224:  qpidd can be crashed by unauthenticated user

    Apache Software Foundation - Security Advisory

       qpidd can be crashed by unauthenticated user

CVE-2015-0224  CVS: 7.8

Severity: Moderate

Vendor:

The Apache Software Foundation

Versions Affected:

Apache Qpid's qpidd up to and including version 0.30

Description:

In CVE-2015-0203 it was announced that certain unexpected protocol
sequences cause the broker process to crash due to insufficient
checking, but that authentication could be used to restrict the
exploitation of this vulnerability.

It has now been discovered that in fact failing authentication does
not necessarily prevent exploitation of those reported
vulnerabilities.

Further, it was stated that one of the specific vulnerabilities was
that the qpidd broker can be crashed by sending it a sequence-set
containing an invalid range, where the start of the range is after the
end. This was an incorrect analysis of the vulnerability, which is in
fact caused by a sequence-set containing a single range expressing the
maximum possible gap.

Solution:

A further patch is available that handles a range expressing the
maximum possible gap without assertion
(https://issues.apache.org/jira/browse/QPID-6310). The fix will be
included in subsequent releases, but can be applied to 0.30 if
desired.

Credit:

This issue was discovered by G. Geshev from MWR Labs

Common Vulnerability Score information:

CVSS Base Score                   7.8
Impact Subscore                   6.9
Exploitability Subscore           10
Overall CVSS Score                7.8

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ