CVE-2010-1244: Cross-site request forgery in Apache ActiveMQ

Summary

02/05/2022
Yes i
Moderate
Not published

CVE-2010-1244: Cross-site request forgery in Apache ActiveMQ. Affects org.apache.activemq:activemq-parent versions < 5.3.1. Fixed in 5.3.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache ActiveMQ is an open-source message broker that implements the Java Message Service (JMS) specification. It provides reliable messaging between distributed applications and supports various messaging patterns. ActiveMQ allows users to create queues for message processing. However, prior to version 5.3.1, it was vulnerable to cross-site request forgery (CSRF) attacks.

Vulnerability Detail

The vulnerability, identified as CVE-2010-1244, allowed remote attackers to hijack the authentication of unspecified victims. By exploiting the vulnerability, attackers could create queues via the JMSDestination parameter in a queue action. This could lead to unauthorized access, data manipulation, or other malicious activities.

How To Fix

Minimum fixed version

5.3.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can consider implementing additional security measures such as enforcing strict access controls, using secure communication protocols, and regularly monitoring ActiveMQ logs for any suspicious activity.

Conclusion

The CSRF vulnerability in Apache ActiveMQ prior to version 5.3.1 can lead to unauthorized access and potential data manipulation. It is crucial for users to upgrade their ActiveMQ installations to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.activemq:activemq-parent →

Share this vulnerability

FAQ

Apache ActiveMQ is an open-source message broker that facilitates reliable messaging between distributed applications.

Cross-site request forgery (CSRF) is a type of attack where an attacker tricks a victim into performing unwanted actions on a web application in which the victim is authenticated.

The CSRF vulnerability in ActiveMQ allows remote attackers to hijack the authentication of victims and create queues via the JMSDestination parameter. This can lead to unauthorized access and potential data manipulation.

Yes, upgrading to Apache ActiveMQ version 5.3.1 or later fixes the CSRF vulnerability.

In addition to upgrading ActiveMQ, users can enforce strict access controls, use secure communication protocols, and regularly monitor ActiveMQ logs for suspicious activity.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.activemq:activemq-parent.

How To Fix

Minimum fixed version

5.3.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback