Friday, May 24, 2024

ApacheMQ Authentication Flaw Let Unauthorized Users Perform Multiple Actions

Apache ActiveMQ is a Java based communication management tool for communicating with multiple components in a server.

It is an open-source widely used messaging service that can be used to send messages between two or more applications.

However, Apache ActiveMQ has been discovered with a critical flaw in its authentication that could allow literally anyone to perform malicious actions on the vulnerable instance.

This vulnerability has been assigned with CVE-2024-32114 and the severity has been given as 8.5 (High).

Document

Integrate ANY.RUN in Your Company for Effective Malware Analysis

Are you from SOC, Threat Research, or DFIR departments? If so, you can join an online community of 400,000 independent security researchers:

  • Real-time Detection
  • Interactive Malware Analysis
  • Easy to Learn by New Security Team members
  • Get detailed reports with maximum data
  • Set Up Virtual Machine in Linux & all Windows OS Versions
  • Interact with Malware Safely

If you want to test all these features now with completely free access to the sandbox:

Technical Analysis – CVE-2024-32114

According to the reports shared with Cyber Security News, this vulnerability exists due to the default configuration on Apache ActiveMQ which does not properly secure the API web context where the Jolokia JMX REST API and the Message REST API are located. 

This arises specifically because the API web request does not require authentication, allowing access to anyone.

Moreover, this could allow a threat actor to interact with the Jolokia JMX REST API and perform actions like producing a message, consuming a message, or purging or deleting destinations using the Message REST API. 

On-Demand Webinar to Secure the Top 3 SME Attack Vectors: Watch for Free.

To prevent this vulnerability, users of Apache ActiveMQ are recommended to update the default conf/jetty.xml configuration file with the below code for adding authentication requirements.

As an alternative, users can upgrade their Apache ActiveMQ to version 6.1.2, which has an updated default configuration with authentication.

Apache has also released a security advisory for addressing this vulnerability.

Is Your Network Under Attack? - Read CISO’s Guide to Avoiding the Next Breach - Download Free Guide

Website

Latest articles

Hackers Weaponizing Microsoft Access Documents To Execute Malicious Program

In multiple aggressive phishing attempts, the financially motivated organization UAC-0006 heavily targeted Ukraine, utilizing...

Microsoft Warns Of Storm-0539’s Aggressive Gift Card Theft

Gift cards are attractive to hackers since they provide quick monetization for stolen data...

Kinsing Malware Attacking Apache Tomcat Server With Vulnerabilities

The scalability and flexibility of cloud platforms recently boosted the emerging trend of cryptomining...

NSA Releases Guidance On Zero Trust Maturity To Secure Application From Attackers

Zero Trust Maturity measures the extent to which an organization has adopted and implemented...

Chinese Hackers Stay Hidden On Military And Government Networks For Six Years

Hackers target military and government networks for varied reasons, primarily related to spying, which...

DNSBomb : A New DoS Attack That Exploits DNS Queries

A new practical and powerful Denial of service attack has been discovered that exploits...

Malicious PyPI & NPM Packages Attacking MacOS Users

Cybersecurity researchers have identified a series of malicious software packages targeting MacOS users.These...
Eswar
Eswar
Eswar is a Cyber security content editor with a passion for creating captivating and informative content. With years of experience under his belt in Cyber Security, he is covering Cyber Security News, technology and other news.

Free Webinar

Live API Attack Simulation

94% of organizations experience security problems in production APIs, and one in five suffers a data breach. As a result, cyber-attacks on APIs increased from 35% in 2022 to 46% in 2023, and this trend continues to rise.
Key takeaways include:

  • An exploit of OWASP API Top 10 vulnerability
  • A brute force ATO (Account Takeover) attack on API
  • A DDoS attack on an API
  • Positive security model automation to prevent API attacks

Related Articles