GHSA-34fp-xvxp-rg22 CVE-2012-6551
Apache ActiveMQ default configuration subject to denial of service
Medium
Maven
- Severity
- Medium
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 7.77%
- Chance of exploitation in the next 30 days. Higher than 94.64% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 2 packages have a fixed version
Description
The default configuration of Apache ActiveMQ before 5.8.0 enables a sample web application, which allows remote attackers to cause a denial of service (broker resource consumption) via HTTP requests.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.activemq:activemq-web-demo | < 5.8.0 |
5.8.0 |
| org.apache.activemq:apache-activemq | < 5.8.0 |
5.8.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.apache.activemq:activemq-web-demo Maven → 5.8.0
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>activemq-web-demo</artifactId><version>5.8.0</version></dependency>- gradle
implementation("org.apache.activemq:activemq-web-demo:5.8.0")
org.apache.activemq:apache-activemq Maven → 5.8.0
- maven
<dependency><groupId>org.apache.activemq</groupId><artifactId>apache-activemq</artifactId><version>5.8.0</version></dependency>- gradle
implementation("org.apache.activemq:apache-activemq:5.8.0")
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
- github.com/apache/activemq/commit/22bc55b9487df98a3c3cb04f99f4618fcba364fe
- github.com/apache/activemq/commit/437ea2f6e58d18837ae0e68dcd2fdadc1fff3723
- github.com/apache/activemq/commit/ced33d2551a040813cb40bd6d36fdd322034fa73
- issues.apache.org/jira/browse/AMQ-4124
- issues.apache.org/jira/browse/AMQ-5033
- issues.apache.org/jira/secure/ReleaseNote.jspa
- web.archive.org/web/20130916074709/http://activemq.2283324.n4.nabble.com/DISCUSS-Act…
- web.archive.org/web/20200228042520/http://www.securityfocus.com/bid/59401
- activemq.apache.org/activemq-580-release.html
- rhn.redhat.com/errata/RHSA-2013-1029.html
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-hf52-78x8-6w3w Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All have an Exposure of Sensitive Information Through Metadata vulnerability | Medium | Also affects org.apache.activemq:apache-activemq |
| GHSA-99qx-5qqr-4j95 Apache ActiveMQ has an Incorrect Default Permissions vulnerability | High | Also affects org.apache.activemq:apache-activemq |
| GHSA-cpw7-g3p5-qrfq Apache ActiveMQ server has an incomplete authorization workflow | Medium | Also affects org.apache.activemq:apache-activemq |
| GHSA-v853-w46p-fv2h Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ have a Code Injection issue | High | Also affects org.apache.activemq:apache-activemq |
| GHSA-hg6c-8mvr-jqc9 Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ have a Code Injection issue | High | Also affects org.apache.activemq:apache-activemq |
| GHSA-8wm6-6fqh-phmc Apache ActiveMQ, Apache ActiveMQ Web have a Cross-site Scripting issue | Medium | Also affects org.apache.activemq:apache-activemq |
| GHSA-mr6m-xj7v-3cv3 Apache ActiveMQ Vulnerable to Code Injection | High | Also affects org.apache.activemq:apache-activemq |
| GHSA-2jp3-2923-9h52 Apache ActiveMQ Vulnerable to Cross-site Scripting | Medium | Also affects org.apache.activemq:apache-activemq |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor