Allocation of Resources Without Limits or Throttling Affecting eap7-activemq-artemis-core-client package, versions <0:2.16.0-17.redhat_00051.1.el7eap


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.27% (69th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-EAP7ACTIVEMQARTEMISCORECLIENT-6099568
  • published5 Dec 2023
  • disclosed18 Apr 2023

Introduced: 18 Apr 2023

CVE-2023-26048  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade RHEL:7 eap7-activemq-artemis-core-client to version 0:2.16.0-17.redhat_00051.1.el7eap or higher.
This issue was patched in RHSA-2023:7637.

NVD Description

Note: Versions mentioned in the description apply only to the upstream eap7-activemq-artemis-core-client package and not the eap7-activemq-artemis-core-client package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

Jetty is a java based web server and servlet engine. In affected versions servlets with multipart support (e.g. annotated with @MultipartConfig) that call HttpServletRequest.getParameter() or HttpServletRequest.getParts() may cause OutOfMemoryError when the client sends a multipart request with a part that has a name but no filename and very large content. This happens even with the default settings of fileSizeThreshold=0 which should stream the whole part content to disk. An attacker client may send a large multipart request and cause the server to throw OutOfMemoryError. However, the server may be able to recover after the OutOfMemoryError and continue its service -- although it may take some time. This issue has been patched in versions 9.4.51, 10.0.14, and 11.0.14. Users are advised to upgrade. Users unable to upgrade may set the multipart parameter maxRequestSize which must be set to a non-negative value, so the whole multipart content is limited (although still read into memory).

CVSS Scores

version 3.1